It does. And what I have seen in there are cases where some distros do well with this being disabled with some kernels.
Most often, this is true with suspend/resume. In those instances, the idea is to prevent the module from failing to resume at all (which was happening on Fedora).
In the case of it not connecting, I want to make sure this isn’t a power saving thing. Once that’s shown not to be a thing, then we can dive into loaded modules, kernel bugs, etc.
This will feel super counter-intuitive. However, I’ve seen power saving do weird, weird things in the past and 8 times out of 10, it’s the culprit for stuff like this.
Regardling blacklist TLP stuff - there is a bit of confusion about this. Despite what you see here, it won’t help with power saving. That said, one could try usbcore.autosuspend=-1 instead of usbcore.quirks. But quirks targets what we want, autosuspend is only helpful with resume.