One thing I like more about Vim is that its ideal for quick edits in the command line. I don't my whole Emacs init for that. Maintaining two sets of configurations on Emacs is not as simple as it should be.

Try configuring your environment so you run constantly within your Emacs, and use tramp to get to those quick edits. I do reach for vim when I'm on like an airgapped or DMZ'd system, so I totally know what you are saying. Tramping out to nearly all my servers has let me retain for longer the threads of flow established within my Emacs session.

Lately, I've been experimenting with CRIU preserving my tmux'd Emacs session state. So unless an OS update hits libraries my Emacs session needs to reload, I should be able to maintain a better relocatable resumable state than even the Emacs desktop alone could.

Run Emacs as a daemon/server and then connect with emacsclient in the terminal. Will start up in about the same time as Vim.

I run Emacs as a daemon but I need two sets of configurations because many colors and keybindings won’t work on the terminal.

You can run multiple daemons of course.

Complexity intensifies... hahaha

emacsclient usually starts even faster than the Vim (even without .vimrc)