As someone who learned all Emacs bindings, went through all the packages, hooked some custom elisp: I am using neovim today.
background:
First editor was vim without configs
Then moved to vscode, then to emacs, then to (neo)vim with some sensible defaults
The reason I am using vim today is because emacs is overwhelming.
You can do anything in it.
...But you can also do _anything_ in it, and that's bad.
Because, depending on your personality, you will find yourself figuring out workflows and tinkering with your config more often than doing things worth the time.
And, more often than not, there aren't any _sensible_ defaults in emacs.
Everytime you open emacs you may feel like "it's not enough".
Using evil mode in emacs doesn't make sense; it is a patch that forces you to do even more configuration and keybinding management.
Use emacs if you find devtooling an inherently interesting problem space
Otherwise you will find emacs gets more in your way than not.
Do note that I do not use any LSP or auto-completion, because it doesn't help as much as you think it does.
I will always be thankful toward GNU/Emacs for lisp and useful term keybindings
Other than that, depending on what interests you, it's just work.
>>2
* magit
Is the only one I miss, but the git cli is fine for 90% of cases
* org-mode
tried it, again, depends on whether or not you like "tooling" - I never got much out of it.
It's _work_ to figure out good workflows.
The above sentence applies to the rest of the things you listed.
Everytime I think about emacs now I just sigh, because it was just so much work