the taproot soft fork was pushed too fast, unlikely past soft forks with over 95% of consensus.
Not at all. The time it took for its preparation process (proposal, implementation, review, testing, deployment) was longer than most soft forks and the threshold was also the same as other soft forks.
just becasue they took "longer2 from proposal-review-testing, boes not mean something should hen be pushed fast into activation where it does not require node upgrades of majority
the whole "backward compatility" softening of consensus years ago has its disadvantages
new stuff can be slipped in that can bloat the blockchain where even as non-standard nodes are to treat it as "isvalid" and not do any validatation on such new funky stuff
where by to undo such things then requires a majority consensus mostly in the form of a MAHF to then fix a rule to then reject formats slipped in without needing a hard consensus activation