So what happens to apachectl, and to people who are used to it?
Well, this kinda sucks. Service-specific control commands are a relic from the past; using supervision or service manager commands to address services is much better - this unifies the interface across services and makes it easy to define distribution policies; and modern supervision systems generally provide better guarantees than service-specific control commands, which are often not much more than three shell scripts in a trenchcoat to hack something that looks like supervision.
That's... not a very satisfying answer, is it?
It's possible to get a better one - but it requires effort. Since apachectl and similar control commands are not usable as is in a supervised world, people who provide the service files - whether the distribution, as it used to be and should still be, or upstream, which for some reason took up that burden and is often doing a bad job of it - should also provide replacements for control commands, written on top of service manager commands.
So, instead of systemd invoking apachectl, it should be apachectl invoking systemctl.
apachectl start➡️systemctl start httpdapachectl stop➡️systemctl stop httpd- etc.
And yes, that requires a lot of writing for someone who supports different service managers - which is what distros should do because monocultures are bad. But the good news is that these can generally be pretty simple shims; this is far from complex or difficult code. 11/12
(Edit: clarity)