User defined rendering engine
You have to target the technically challenged, we get that.
But if you made the renderer a separate module with proper APIs then technically competent people who want to use it for collaboration could install their own renderer that handles specialised requirements properly. For example I wrote a renderer for printing from VS Code - it wouldn't be hard to adapt that, and then not only would I be free from the stupid emojis, I could use language specific syntax colouring in code fenced blocks and in particular use TeX markup for equations.
You don't need to bother with integrating settings with your settings page, users of a custom renderer won't mind editing appSettings.json in fact they'll be delighted that you can no longer mess everything up with each forced update.
To anyone thinking about voting this up, I promise that if they support it I will build that renderer and open source it so you can use it. No emojis, no voice bubbles, syntax-coloured code blocks, enhanced markdown not a half-baked subset.