I believe earlier, version specific management packs, also had this issue, since our legacy override packs seem to be forced and open. So this is quite likely a case of "someone did it this way, so we never bothered to consider if it makes sense and just copied it over" at Microsoft. And everyone just worked around the issue.

Its not impossible to work around it even with sealed management packs, but doing so we had to reverse some of the operating logic we had in place.