Here’s the part which matters:
wSpeedsSupported 0x000e
Device can operate at Full Speed (12Mbps)
Device can operate at High Speed (480Mbps)
Device can operate at SuperSpeed (5Gbps)
This particular device does not reach 10 Gbps because it does not have that capability. There is no USB HUB capable of improving that speed.
If you look at this, then you can see that the root HUB could achieve 10 Gbps, but the reason the device does not reach this speed is due to device design, and not due to signal quality:
/: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=tegra-xusb/4p, 10000M
|__ Port 3: Dev 2, If 0, Class=Hub, Driver=hub/4p, 10000M
|__ Port 2: Dev 4, If 0, Class=Vendor Specific Class, Driver=, 5000M
Keep in mind that Bus 02, Port 2: Dev 4 is not the only device on that root HUB. It like Bus 02, Port 3, Device 2 is a HUB plugged in to the USB 3.2-capable root HUB, but that HUB does not itself have anything attached. Had something else been attached via that HUB, then it would have traffic competing with your specific device, and a different root HUB would help. As is, I don’t think anything you do can help that one device (it has its own root HUB and is running at that device’s max speed).
Trivia: Older USB2 and earlier evolved such that older standards were also serviced by a single USB controller. This means that a single chip on the old ports handled USB 1.0, 1.1, and 2.0 by reverting to the required mode on any given device. Starting with USB 3 a single controller works for only USB 3.x devices. The way a USB 3 port handles legacy USB 2 and earlier devices is by actually rerouting the signal to a separate USB 2 controller. In other words, any USB 3.x device is purely USB 3.x and any legacy device goes to a separate chip. You could plug in a USB 2 device to your USB 3 HUB and it would show a USB 2 root HUB rather than the USB 3 root HUB. Traffic would not actually go from the USB 2 device to the USB 3 HUB.