Taproot finally reintroduced the op_ver functionality without the flaw.
Considering that the only versions that I know of in Taproot is the defined Tapleaf versions (currently only 0xc0 is defined) and the fact that OP_VER seems to be pushing the protocol version to the stack (doesn't look like the value depends on
the stack itself.), and the fact that Taproot interprets 0x62 as OP_SUCCESS, could you explain what you mean here?
All OP_SUCCESSx opcodes can be redefined (once) using a soft-fork to make it conditionally succeed or fail. For now nearly all of them just abort validation with a success code immediately, before anything is even evaluated.