What evidence do you see in ioreg that the Logitech drivers are hooking USB?
With more details, I will add it the FAQ.
Waiting 10sec to upload firmware will likely cause the native BT drivers to fail...
With drivers installed (LogitechUnifying.kext and LogitechHIDDevices.kext in L/E), every time I plug any mouse or HID wireless receiver into USB, the device starts working, then freezes for two seconds, then starts working again.
The same freezing behaviour happens just after a wake from sleep.
My idea is that this driver messes with the ports, maybe to increase polling rate from 125hz.
With driver removed, I get 10X slower mouse and it does not freeze upon insertion or wake from sleep.
The kexts listed are bundles with Logitech Control Center pref-pane, which I uninstalled, leaving only the two kexts.
Since the same issue happens with AFT or chrome, I think that every driver that blocks or polls the USB ports upon wake make the uploader fail.
As a proof, with only the BT injector (no firmware loaded), bluetooth worked with limited functionality, but 100% consistently, even with thise Logitech drivers enabled.
It seems like there's a race condition, or the uploader tries to reset the device while the USB port is unresponsive, then resulting in 2 device instances.
This happens with your uploader, and also with EmilyDinesh one (closed source).
I think this race condition should be investigated a bit.
I can help you troubleshoot the issue.
If you have a old Unifying wireless receiver somewhere, I can send you/tell you how to extract the drivers so you can hopefully reproduce this issue.
Can you confirm that your Bluetooth does not crash after wake (from 5min+ of unplugged sleep) if the Logitech drivers are not present?
Because I had the same problem (excluding the duplicating BCM20702A0 device, and also strange that your webcam is not present there - have you disabled it?), without ever having any 3rd party peripheral drivers installed.
Camera disabled in BIOS.
Look in L/E for third party extensions, do a complete cleanup. We identified ATF, Chrome and likely LCC as "usb-hookers", but the issue may happen with other drivers polling USB at wake.
Hopefully, we can fix the BT uploader to stop avoiding these apps as a workaround.