All that info can be made available at a higher level. The only reason to do it at a lower one is to reduce surface area where software bugs could destroy the speakers.

> Our implementation, speakersafetyd, monitors feedback signals from the amplifiers, estimates speaker voice coil temperature using a two-stage thermal model, and reduces the hardware speaker volumes when the speakers get too warm. We also have kernel-side interlocks to disable or limit speaker volumes if speakersafetyd is not running or non-responsive.

This is the only part that seems to need to be low-level, anything else could be done at a higher one, generally EQ type settings like 'loudness'.