Supervision is great. Service management is great. But with the advent of all this, how do service-specific controllers like apachectl fit in? What do they become?
Well, they don't fit in well is the problem. There is basically no purpose for them anymore.
Starting a longrun httpd service would be done via systemctl start httpd, and the httpd service would be properly started under a supervisor, without auto-backgrounding. The httpd process would, ideally, be reloaded with a SIGHUP, gracefully killed via a SIGTERM, not-so-gracefully killed via a SIGQUIT or any equivalent semantically-adjacent signal (not SIGKILL, that's only the very last resort), and so on - conventions that are more than 30 years old, that a lot of software still follows, and when the process' behaviour doesn't match the conventions, the supervisor can be adjusted to send different signals (most supervision systems, including systemd, can do this). httpd would then fully benefit from being supervised; and the whole self-management layer can go.
The drawback is that if the server is Apache, the apachectl commands then become incorrect, because apachectl does not know of the supervised instance of httpd; apachectl start would start its own instance and do its own thing, completely unaware of the supervision framework. More importantly, apachectl stop would not work, because it would try to stop a nonexistent instance. Also, if it somehow worked, the supervisor would be unaware of the external apachectl stop command, and would only see the httpd process die; unless configured otherwise, it would treat that death as a temporary error and restart the process.
There is definitely a conflict here. 7/12