There's script & executable invocations inside systemd service files as well. They're simply handled differently. Some setups use dedicated units to just do `modprobe X`, and have "easy" dependency management. Some are replacing udev rulesets with systemd units, none of which are "orders of magnitude smaller".
Just saying, the de facto ways of using systemd are starting to diverge a lot from the intended behaviour. And of course, the de facto usage is what we'll judge each piece of software's merits on...eventually.