I just rage quit

There's a misunderstanding here. Rubberbanding is the solution, not the problem. The problem is things being out-of-sync, which we'd all like to have less of. People in this thread seem to be equating the two.

Something rubberbands when the game's detected it's fair enough out of sync to require it, thus returning it to it's correct, in-sync location. If this happened more often, things would rubberband more, but many of of these would be smaller distances, or off-screen, and thus less visible to the player, and rubberbanding more frequently would mean things were much less out-of-sync in general.

As an analogy, imagine an apartment building that catches fire frequently, and if the fires get big enough, the sprinklers detect this and douse the fire.
When Chris says he wishes the sprinklers went off more often, he's not saying he wants more fires to occur, he's saying he wants the sprinklers to find and put out smaller fires before they become bigger ones.

People have a tendency to think of rubberbanding being the problem, when rubberbanding is the act of fixing the actual problem (things being out of sync). Rubberbanding more often would prevent the sync issues from getting as big. Of course it's also desirable to reduce the actual occurring of sync issues in the first place, but there's nothing wrong with wanting the game to detect and fix them more often.

Sync issues can never be completely eliminated, so methods like rubberbanding are needed to combat them. If the game had no rubberbanding, that wouldn't mean everything was always in sync, it would mean everything was out-of-sync constantly and would never get back in-sync.

There's a trade-off between the fact that rubberbanding fixes the issue, but also makes the fact the issue occurred more visible to the player (just as hearing the sprinklers go off in the kitchen might tip you off to a fire you didn't know was there).