???? No. Not even close.
You're making the case that every WHM player [or those of whichever other job you'd chose to sacrifice] wants to have access only to the shallowest of kits and that --despite their being able to use as much or as little of a kit as they like-- they'd be somehow so perturbed by even seeing anything more than the barebone basics we have now that they'd lose out.
But you've provided no evidence for any of those claims or their underlying warrants.
You are the one saying Job X must be shallowed out so some hypothetical player -can better pretend they're not spending less effort for the same result --sacrificing the one for a hypothetical sub-group, as opposed than even than many-- rather than their being able to do more instead doing only so much as is (A) needed in what content they're comfortable with and therein (B) comfortable for them.You've provided no rationale as to why players would be unable to simply choose how much of a given kit to engage with and ignore what they don't.
You've provided no rationale as to why having a kit larger than one wishes to engage with significantly worsens a user's experience.
You've provided no evidence that most WHM players like being 'just basic' and that keeping the job low-ceiling would therefore be preferable over giving them more to work with if they so desire.
You've provided no evidence that people pick jobs for specifically being simple or having low ceiling (which is just a lack of anything more) over their vibe, flow, features, and/or aesthetics (which is the only way you'd be favoring the total healer population as a whole by screwing over WHMs [or whichever other job you'd choose to sacrifice]).
You're asking to kneecap Paul specifically so others can use him as a disabilities role model, rather than just letting Paul choose not to run when it's neither necessary nor desirable.
If, as you say...The only solution - absent that - which I can see would be to make one healer not require it. Then players on that healer simply don't have to worry about it, and no one will be blackballing them since they'll be doing the same general overall performance as the people who are pushing optimization playing the other Jobs.
...then what would it possibly matter than WHM isn't likewise so trivial in its kit? Why does it have to be neutered if using a greater extent of its available tools, nuances, optimizations, etc., is unneeded?the optimized difference is not trivial/unneeded
It's not the "only solution." It's not even a solution whatsoever.