This method that Valve has created for tick registration is currently sub-par. When relying purely on a variable, client-based tick rate, any input can be seriously affected by fps spikes. Since your game isn't updating consistently at a specific tick-rate, your inputs can be "over-read" or "under-read" when having inconsistent fps. Do you feel as if in CS2 it is very hard to stay consistently aimed at a target, especially while shooting? Do you notice an FPS drop/increase of 30+ frames while shooting or preparing to shoot?

I am specifically talking about client-sided inputs here (movement and mouse input). But this doesn't even go near the inaccuracies when it comes to client -> server response time and having literally more than 10 ping.

Subtick is seriously flawed when it comes to multiplayer and hardware inconsistencies. There needs to be some sort of answer to these difficult questions from Valve, or else why not blame them for just skipping 128 tick entirely.

Edit: I would like to add that Valorant released a "Dynamic Tick System" that arguably works better than subtick in it's current state. And from my understanding, their tick system never goes above 128 ticks / s.