Your argument highlights its own flaw; changing your editor opens up a world of tooling that's certainly adequate for most use cases you can throw at it, but it also requires either discarding or (worse) un-learning all of the tooling that you've learned for your current editor.

For example, I'm perfectly content to use nvim as my primary editor, and this was born out of having to develop for and administer literally tens of thousands of linux servers professionally. I have all the plug-ins and configuration necessary for productivity on my development machines, and when I'm on a remote system ad hoc editing a configuration it already has a built-in lightweight version of the editor I'm already used to.

If I switched to Emacs locally, I'd still have to maintain a working knowledge of vi and context switch when in a remote shell. Changing to Emacs would require more cognitive bandwidth when the whole purpose of "switching for org mode" is to reduce mental load.