As I already told you in the issue, we have these checks now. This breaking change was introduced last year in August and since then, we have increased the number of tests. Especially when it comes to ensuring that storage items do not silently change. The try-runtime checks for example now decode the entire state, which helps detecting these kind of bugs. Especially when it comes to this bug you mentioned, I should have requested that we bring up a fix. Sorry for that!
I also get this and we are working hard to bring up even more tests that this is not happening again. The entire release situation should hopefully greatly improve with the introduction of the new release process. Especially as there will be less releases and we can focus better on backporting, if required. I can coordinate internally that this fix gets backported.