First of all, the reason for this behaviour seems to be USB specific. Kernel.org ([here][1]) states the following:

> When USB 1.1 devices plug into USB 2.0 hubs, they interact with the
> EHCI controller through a “Transaction Translator” (TT) in the hub,
> which turns low or full speed transactions into high speed “split
> transactions” that don’t waste transfer bandwidth.

Since there is no specific USB 1.0 module (the USB 2.0 will handle USB 1.1 devices), which could be black-listed, this is no option.

The product page states the device as USB 2. ([here][2])
Since the device is not USB 3, we cant unload all modules and load the XHCI first, to let it grab the device.

Please try:
 udevadm trigger
And see, if it get recognized correctly.
 [1]: https://www.kernel.org/doc/html/latest/usb/ehci.html
 [2]: http://signature.wacom.eu/de/produkte/hardware/stu-530/