I ran into this problem with a USB Video Capture device. My solution that worked was that the USB hub that I placed in between the device and computer added a non-boot detect barrier. You would think that the hub would be completely passive, but the computer detects the hub vs the device that is plugged into the hub, and the hub chipset doesnt have an instruction that initializes giving a false positive as a bootable device.
So I was then able to keep the video capture device plugged in all the time so that I didnt have to remember to unplug it when done before shutdown so that the next time I booted the computer it wouldnt get hung up past the Biostar splash screen of the computer and sit at a blinking cursor forever.
If you want to keep it plugged in all the time without having to unplug it and still have BIOS always set up to support of a bootable USB stick, a USB HUB might be your solution the same way that mine is. I am using a Belkin USB HUB USB 2.0 but any USB HUB "should" act as a boot barrier for devices connected to the USB HUB. * My USB HUB is an older 7 year old hub and I am not sure if newer ones would initialize at boot and pass devices that are bootable on it to the computer. To me it wouldnt make sense to allow for this pass through because say you have 2 USB sticks connected to it and both are bootable, it would come down to whichever port interrupt is the first for the USB HUB or USB stick first handshaked with the HUB chipset. So newer hubs if you get a newer one should still work as a barrier, but there is that slight chance that some manufacturers HUB would pass through saying that a bootable device is connected to it. Im not familiar with the low level protocol that is used at boot to find more info on this to search for a hub that doesnt support the USB low level communication protocol. If you happen to have a USB hub on hand though its worth a free try at a solution, otherwise USB 2.0 hubs are cheap and it might be worth the $10 or $15 etc at a gamble to fix this with the HUB method.