There are now two management layers to the service: systemd and apachectl. And they have to agree on its state - and they don't. Because from systemd's point of view, it is a oneshot, not a longrun; it stopped as soon as apachectl start exited; so "reloading" makes no sense since the service is "not active". That is what happened to @mcc .
And this is where systemd is wrong. If it has been given an ExecReload= directive, it should just run it, even if it thinks the service is inactive. If it really is, the reload command will error out and systemd can report the error. But systemd doesn't do that, because it doesn't understand that it's handling a oneshot - and ExecReload= only works for longruns. systemd does not handle the difference properly; if it did, the presence of an ExecReload= directive in a oneshot service file would at least raise a warning.
Conclusion: systemd is bad, but we already knew that, and more to the point, this unit file is garbage, and simply does not work. Did nobody test it? Does anyone in FOSS test anything anymore? 9/12