Often more than not, the certificates need to be post-processed before they can be used by applications (e.g. keytool etc.). It would help if the postsave command (often a wrapper) would have access to e.g. the location of the certificate and private key, and potentially other information that is available to Certmonger.
This would greatly enhance the functionality of postsave commands and could eventually lead to standardized wrappers for Certmonger taking care of keystore integration or necessary conversions and other nice functionality admins need to get a complete working end-to-end solution.
The trick is in identifying those things that would be relevant. Along with the PEM cert and key paths the NSS database and nickname would be needed at a minimum. Depending on what operations are done the PIN and PIN file would be needed.
A poorly written post-command script could lead to vulnerabilities and leaking of information.