Of course the irony of it is that we aren’t trying to “skirt the rules” or do anything that can be considered even remotely dodgy.
We are following Microsoft’s established rules (linked previously) exactly, with the main goal of installing a pure Microsoft driver (WinUSB), that is pretty much delivered by the system anyway.
But the sad truth is that Windows was never designed to install the generic USB driver it provides against a device that the user wishes to access in a generic manner… which forces us to jump through hoops that people who produce drivers for specific devices are unlikely to ever require, but that end users actually very much want, on account that Microsoft failed to offer a proper solution for them (outside of WCID, but WCID requires the provider of the device to already have planned for its use with a generic USB driver).