Atleast with the case of xHCI the 10ms is actually a minimum for both -- the specs do not indicate a maximum for the hardware to resume at all.
That's not how specifications work. Both sides are required to obey the spec for things to work. A minimum for one side is a maximum for the other side.
It's like we have a lunch break specification. The specification says that on a lunch break he must wait a minimum 30 minutes before sending the employee more work to do. This means the employee has a maximum 30 minutes to finish lunch.
What is happening here is that the employer (the computer) is obeying the spec. It's waiting the required minimum time, then sending a message "here's some work to do". The employee (the USB device) is late, still lingering out to lunch (in violation og the lunch rules) when he gets the work message. This employee (device) is responding "I'm not ready, I quit" and goes home (device disconnect).
-