not exactly... Look back at the development of the various threads on this topic. Theystarted out with what amounts to "this is a thing, I don't begrudge sorcerers getting it... but it does step on the wizard class toes a bit & I think wizards should get something to call their own" > "omg wizrds are too strong gitgud learn2code, wizards can suck it" > "uhh that's rediculous because so much of what the wizard has of their own can be duplicated ()literally or effectively by other classes, here's some examples of stuff they used to do in past editions before wizard & sorcerer got stuff in 5e" > "no suck it long suck it hard".
It's less of a "sacred cow mechanic" than acceptance of the fact that one side is largely arguing in bad faith trying to point at class features in isolation for balance of class A vrs that very myopic & cherry picked view of isolated feature from classB while ignoring & dismissing arguments that class A has a number of class features to call their own because of that cherry picked feature. Since one side of the discussion is unwilling to even consider discussing what something that wizards should get, the discussion falls back to why wizards should get something.