Instead of adding a line in my httpd.conf, I would that Cerbot to create a static link between two files.
If you don't want Apache automation, don't use --apache – use certonly --webroot instead.
certbot certonly --webroot -w /srv/http -d example.com
For web certificates, I like aliasing all vhosts' acme-challenge locations to a single path, that way I can continue using the same -w /srv/http regardless of vhost (or regardless of whether a vhost has been defined or not yet):
Alias /.well-known/acme-challenge /srv/http/.well-known/acme-challenge
(This is technically optional – you can instead define the HTTP vhost first, then get the certificate using the appropriate -w path, then finally define the HTTPS vhost, but that's a bit more work.)
It sounds like you plan on using this for a non-web certificate, i.e. without there ever being an Apache vhost. In that case use the default vhost's DocumentRoot as the webroot path.
Either way, certonly lets you obtain certificates using HTTP-01 challenge without actually making Certbot add anything to the web server's configuration. Then you can use --deploy-hook (if it works) or a custom wrapper script to do the rest.
Also, remember that Certbot is not the only ACME client for Linux. Other implementations (Lego, acme.sh, acmetool...) might be more convenient for certain use cases.