I do wish I could find a not stupid priced version of this concept that does USB 3.1
I'm the maintainer, but I can only take credit for updating a single line, uploading to GitHub, and doing PR's (mostly to the README) every once in a while.
Azure Kinect DK depth cameras had a firmware/hardware issue that would let it get stuck every now and then, and it would have to be power cycled. You'd imagine it'd be easy, but it was surprisingly hard. Ended up getting a new usb hub that supports power cycle...
For that rare event, it doesn't seem worth writing code to power cycle a single USB peripheral (and then write and test all the code to clear the error states at each level of the stack and bring that peripheral back up again).
Instead, power cycle the entire system. Have a small hardware watchdog which, when not being tickled, will power off the whole system for 5 seconds and power everything back on.
Write code to periodically tickle the hardware watchdog when everything is 100% healthy, or when 3 reboots have happened in short succession (you'd prefer the system up with 90% of the hardware working than bootlooping).
It sounds to me like the author genuinely wants to have a discussion about some of the quirks in the USB protocol. I don't see anything wrong with pursuing all available options.