No, it's just bad policy. The correct design on modern "intelligent" buses is very simple. You standardize a class of device, and then you implement that class, OS vendors supply a class driver that works, out of the box, with every device in the class.
USB Mass Storage is the worst case of that approach (vendors with different ideas of how to solve it just agreed to differ and the standard offers all combinations of their preferred methods) but it's still better than the alternative.
Other approaches are crazy, they produce a worse user experience and usually introduce perverse incentives that make life worse for everybody.
If there are in fact "issues" with "vanilla USB" you don't fix those by having every single vendor hand roll their own attempted workaround and ship each of them.
Your approach doesn't result in "a working device" for most users, it results in the situation where you need to buy a new device, to get a new driver, to fix a purely software bug that could have been fixed in the class driver covering your old device instead but that was less profitable and priority #1 is always to bow before the almighty dollar.
Every time Windows ships a new version, users with hardware that worked fine but alas, wasn't shifting too many new units through retail, find now it doesn't work. "Buy a new one, then you'll get updated drivers" people like you cry. More landfill, for no reason.
Real users hate this experience and are relieved when you tell them that some device they're getting doesn't "need drivers". Of course it does actually need drivers, it just uses the OS vendor's class drivers, which work out of the box and are properly maintained, but the user experience is of relief.
Unlikely to be an issue with a stick, but very possible with an external drive.
So searching for a device specfic driver is a very sane default here.