"/tick rate" command is inconsistent (can slow down player movement but can't speed it up)

WAI per changelog: https://www.minecraft.net/nl-nl/article/minecraft-java-edition-1-20-3

Setting a tick target lower than the default 20.0 will also cause the players to be simulatedat a lower rate (including player movement and input controls), whilesetting a higher tick rate will cause the players to be simulated at the default rate of 20 ticks per second to maintainthe expected responsiveness of the game, but can cause artifacts in entities interpolation.

I KNOW... I read the changelog and it is still dumb and confusing. Mojang is just refusing feedback at this point.

I NEED to know WHY this is the case, not be told that this is the case, because yeah, obviously.

Why isn't the player movement completely separate from the tick but SOMEHOW arbitrarily separate when the tick is higher than 20? This literally breaks any sort of consistency between the player and the actual tick rate, either REMOVE the player movement from the "/tick rate" command completely or make it also speed the player up for consistency.

Look, someone needs to say it: Mojang needs to actually listen to feedback. I'm tired of Mojang literally not doing so and so is literally every other redstoner when Mojang made Copper Bulbs "mOrE cOnsIstEnt".

If Mojang is willing to destroy a good redstone component for "cOnsIstEncY", then I expect Mojang to take actual consistency very seriously.

You are told why it is like that in that very quote, to maintain responsiveness of the game.
This site is not for feedback, nor complaints.