But, why? It'd be boring and very limited.
Maybe but bitcoin is not like Windows where you can just not support the older operating system anymore.
It would be better if I quoted him directly:
The script is actually a predicate. It's just an equation that evaluates to true or false. Predicate is a long and unfamiliar word so I called it script.
The receiver of a payment does a template match on the script. Currently, receivers only accept two templates: direct payment and bitcoin address. Future versions can add templates for more transaction types and nodes running that version or higher will be able to receive them. All versions of nodes in the network can verify and process any new transactions into blocks, even though they may not know how to read them.
The design supports a tremendous variety of possible transaction types that I designed years ago. Escrow transactions, bonded contracts, third party arbitration, multi-party signature, etc. If Bitcoin catches on in a big way, these are things we'll want to explore in the future, but they all had to be designed at the beginning to make sure they would be possible later.
All that would be fine but bitcoin is now kind of carrying alot of baggage from legacy things. Not only do we have Script, which was the original "programming language" of bitcoin but now they have Tapscript. Taproot is supposed to give all these extra benefits. If this were Microsoft and a new version of Windows they would do away with backwards compatibility with Script and just go with Tapscript but we can't do that. The longer time goes on and the more "upgrades" that occur, the more excess baggage bitcoin is going to have weighting it down in my opinion. And that can't be good. Alot of inefficiency there...

He really had put the effort to create Bitcoin the
right way.

what are you talking about? the right way is how Microsoft does it and how any reasonable company would do it.