Both Emacs and Vim are usable in the default state, but there's much much more you can get out of them. As opposed to most IDEs, which usually have one proper way to use them, both Vim and Emacs thrive on configurability. On the flip side, that means that you're going to spend time setting up and maintaining your config. If that's not something you can endure (or even enjoy), you might want to leave it be.
As far as I can tell, that's also the main reason both are often overlooked in CS classes: The goal of most professors teaching programming is to actually teach you a language, not explain an editor for a couple of weeks.
Edit: I'd also say that Vim bindings are something where "learning by doing" is the best way to get going, and I'd assume the same applies to Emacs hotkeys. If you want to use them effectively, you'll want to develop muscle memory for the most common actions, so they are a great thing to pick up while you're actually working on stuff.
I'd say the main benefits of learning emacs or vim today are:
1. Exposure to the history of systems they embody.
2. Experiencing the philosophy that customizability should be a key characteristic of your tools and work environment.
For the first, deep use of emacs will teach you about using lisp in a non-academic way; self-documenting systems; modularity; maybe even the unix command line. Oh, and the indisputable fact that your caps lock key should be remapped to Ctrl. :)
For the second, you have a fair bit of customizability in JetBrains but it's nothing compared with emacs or vim. In both of those there is incredible power to modify the behavior of the environment, and the incredible range of ways this power has been applied is a testament to its design.
My advice is to use what everyone around you is using and focus on making cool stuff.
I avoided starting w/Spacemacs or Prelude defaults but you may want them https://github.com/bbatsov/prelude
Emacs you'll find most productive if you live in it, so aside from development where you get your SQLI shell or whatever, also using magit, using pdf-tools to read papers, reading project mailing lists, using org-mode for billing if you're a freelancer, scripting your shell (and now your packages too https://alezost.github.io/guix.el/ ) ect.
On the other hand, JetBrains tools are supposed to be very nice.
I'd say pick one thing and learn it well.
On the other hand if you're a front end Web dev or an Android dev there is probably not much point except from a curiosity point of view
I have no particular reason to want to jump into an IDE, which I imagine is what you're recommending instead. Vim acts as my IDE without much effort. I have a linter, syntax highlighting, etc.
I won't sing the benefits of vim here since they should probably be well-known in this thread, but editing code without vim movements is, to me, a nightmare.
I'm not sure what you think would be different in another editor.
Many IDE's also provide Emacs-like keybindings as does Bash by default. The ability to maintain a consistent user interface may or may not be worth the Emacs learning curve. Org-mode is another thing that may or may not be worth the curve.
That said, I do definitely recommend it to people on a case by case basis (Power users, command line gurus, mouse haters, etc). Those who make it over the initial learning hump tend to really love it.
I won't be quitting anytime soon, but wouldn't recommend it either.