Knuth (the grandfather of modern programming) used warn against "premature optimization" in computer science - that is spending time optimizing code in V1 of the codebase is probably futile because as the code (and requirements) matures, you will find you shot yourself in the foot.

I'm happy we didn't prematurely optimize bitcoin and instead it worked out where Satoshi took out a bunch of OPCODES early on (like CAT) and left us with a more sparce set of tools.

Its not clear why any of these OPCODES are really needed. I appreciate that things like OP_CTV are probably fairly low risk and offer good expressiveness - HOWEVER, lets suppose that CTV is a hit and offers no bugs.....so are we happy with more things going onto layer1? Are we ok if fees go up 50% to handle all the new "smart contract" features we've added?

Lastly, there is a social cost: We must acknowledge that any such initiative is going to cause a bit of a public fight...there are more stakeholders than just the group of devs being included on these "beauty contest" polls. Such a public fight is going to come at a bad time with nation states and large institutions starting to adopt bitcoin. The enemies of bitcoin are going to FUD any of these efforts and will push lies and fear mongering on social media about "new bugs" they've found (which may just be total lies, but the goal is to simply cause more uncertainty).