Reschedule after many cases of eating cycles

All of these eat enough cycles they could cause issues in a loop, and I'm pretty sure they would reschedule.

I didn't individually test them, though.  Fixes #6302.

-[Unknown]
We currently, even with this change, wake +9ms too late in the pure spin case, at +59967... I think it's only waking on vblank or something right now.  I wonder how often the timer/interrupt should run, or if it should really be triggered by the timeout.  The above wake seems pretty accurate.

-[Unknown]