Hi @epopen,
No, currently there is no such option in Certbot. I believe that there was another thread proposing it. Two reasons that dry-run doesn’t run deploy hooks are (1) the test certificates are currently not actually saved to disk in the expected locations, and (2) if they were, they would be untrusted test certificates, so deploying them via deploy hooks could result in deploying invalid certificates to a public web service!
Although it issues new certificates and thus counts against rate limits (and might not be a good option if you’re close to hitting the rate limits), you could try something like certbot renew --force-renewal which will cause a complete renewal process right away, including running all of the associated hooks.