That's not what I would describe as "resolving a license compatibility issue"
"TAINTing" a driver/code doesn't mean it's blacklisted, it means it can't be upstreamed into the GPL codebase. It means that if you build a Kernel with it, it's no longer considered OSS-friendly.
There are plenty of legitimate and viable codebases that use TAINTed kernels. The DoD, various government entities around the world, some commercial interests, etc.
Huh, so Tuxedo developed their own ITE 829x kernel driver.
I have a Clevo based laptop, similar to the ones they sell. Years ago I reverse engineered the keyboard's features and wrote a user space driver.
https://github.com/matheusmoreira/ite-829x
I interacted with Tuxedo quite a few times back then while I was figuring this stuff out. They even sent me source code for a pre-release version of their Electron app. It didn't help much in the end but they proved to be much nicer and more responsive than other manufacturers and even Clevo itself.
Wish they'd emailed me about their driver. I could have helped develop it, especially if they had given me documentation.
I briefly explored the idea of turning it into a kernel module and contributing it to the kernel. While reading Linux driver source code, some comments gave me the impression they'd prefer code remained in user space if possible. Since I already had a working user space driver, I decided not to contribute it.