No. As the systemd people themselves wrote twice over, once in their `telinit` manual and once in their `runlevel` manual, runlevels are "obsolete". You can forget about runlevels.

These things do not actually exist in systemd at all, outwith a few compatibility shims. 

* There are some symbolic links for target names, but these targets are never actually used by systemd proper. 
 * Rather, the bootstrap process employs a `default.target` (and thence one or both of a `graphical.target` and a `multi-user.target`), a `rescue.target`, or an `emergency.target`. And the shutdown process involves a `shutdown.target`, a `reboot.target`, a `halt.target`, or a `poweroff.target`. _No run-level targets are involved_ in either bootstrap or shutdown.
 * The `telinit` command, which one might think uses the compatibility symbolic links to map its command-line arguments, does not do that either. There's a hardwired table in the source code of the `telinit` program, and the numbers `2`, `3`, `4`, and `5` as arguments to the command are hardwired to map to `multi-user.target` and `graphical.target`.
 * `systemd-update-utmp` also has an internal hardwired table.
* There is no "init table" of runlevel stuff. systemd is only compatible with van Smoorenburg `rc`, not with van Smoorenburg `init`.
* There is no "current run level" value maintained by systemd itself. Rather, the almost wholly undocumented `systemd-update-utmp` command operates internally in terms of the activation states of `rescue.target`, `multi-user.target`, and `graphical.target`.
* `systemd-sysv-generator`, systemd's backwards compatibility service unit generator, merges the `/etc/rc[234].d` directories into just the one `Wanted-By` relationship to `multi-user.target` in generated service units. There is no actual reference to run levels in the generated service units. (There used to be, years ago, but the systemd people found that this went wrong, because they weren't being referenced anywhere else.)

If one is a user of a system that builds systemd as did Arch Linux for the questioner at "https://unix.stackexchange.com/questions/389289/", one does not even get the compatibility shims, and commands such as `init 0` result in the "native" systemd behaviour, which is to complain that the command has been incorrectly invoked.

# Further reading
* Lennart Poettering et al.. _[`runlevel`](https://freedesktop.org/software/systemd/man/runlevel.html)_. systemd manual pages. Freedesktop.org.
* Lennart Poettering et al.. _[`telinit`](https://freedesktop.org/software/systemd/man/telinit.html)_. systemd manual pages. Freedesktop.org.
* Lennart Poettering et al.. _[`bootup`](https://freedesktop.org/software/systemd/man/bootup.html)_. systemd manual pages. Freedesktop.org.
* Lennart Poettering (2015-02-08). _[everywhere: remove configurability of sysv runlevel to target mapping](https://github.com/systemd/systemd/commit/d5d8429a12c4b1ef0dcd226c0904f00f4fa4898a)_. systemd. github.
* https://unix.stackexchange.com/a/196014/5132
* https://unix.stackexchange.com/a/196197/5132
* https://unix.stackexchange.com/a/233581/5132
* https://unix.stackexchange.com/a/211927/5132
* https://unix.stackexchange.com/a/392612/5132
* Jonathan de Boyne Pollard (2015). [_`/etc/inittab` is a thing of the past._](http://jdebp.eu./FGA/inittab-is-history.html). Frequently Given Answers.