Sure, like actually keeping a maximum counter that really counts the maximum, and for example gets reset to 0 on reading? That at least was my naive expectation...
IMHO the current code is used, because it is computationally cheap, addition subtraction and a few shifts is something even a lowly MIPS cpu can afford for non-essential things like statistics (these are only collected for humans to reason over). That said, I still think a true re-settable maximum would be god to have (and the reset does not need to be super precise temporally). I guess I will need to understand how tc -s actually reads these values, to understand whether a "consuming" read for max_delay is easy to implement or not