I think you misunderstood me.
Moderators wouldn’t be moderators if they didn’t want to work for users. Moderators can spend all of their free time or a significant amount of their free time on helping users and moderating, including accepting or rejecting posts, reading long AI-generated posts to find out if they are AI-generated so they can make sure only real users’ posts get the deserved attention, and formatting posts so other users will at least try to help even if they can’t. They also help users so that next time they can write their posts better. So it is far from trying to get a comfortable environment for moderators while making things harder for users. Quite the opposite. But they can make things easier for users only if they have time and if they have working tools. Making things harder for moderators will eventually make things harder for users as well.
So my point is exactly that moderators see and understand why WYSIWYG could be a good feature, but if the overall effect is that posts are broken, unreadable, and helpers (including moderators) can only ask the users looking for help to format their posts because only they could know what the original content was and they have the file or terminal output where they copied it from, then people operating the forum have to make decisions that will get the most out of the features and at least temporarily disable what makes things worse and harder for everyone.
Users often ask a question, and if they see their post was broken and we ask them to fix it because they can do it only, they go to StackOverflow or anywhere else.
My comment on markdown that you quoted was only to say that it was the original problem that moderators could continue to handle until the Rich Text editor is fixed instead of having multiple new problems and still have to handle the old, original, since even if people started with the Rich Text, I saw signs that they switched back to Markdown and that broke the post.
So while focusing on helping users, I was talking about how that can be done and how sometimes admins may need to decide what is best for the community. Similarly, how you wouldn’t leave products in grocery stores that make people sick because you want to give them a choice. You would call the product back and investigate.
I did not 
It is hosted by Discourse and was enabled.
Turning on the new composer
The rich editor is enabled by default for all communities . When you or your members open the composer, you’ll notice a toggle in the toolbar. This lets you switch between the classic Markdown-only mode and the new rich text editor.
But this specific case is not important. It can be discussed in its own bug report. I just wanted to share my thoughts about when and why making a feature optional could be useful in general, even if it is disabling Markdown or Rich Text. I hope I could clarify it, and I’m sorry I confused you in the original post. 
