Using the optimize() and frequencies() calls, it’s pretty clear that counterpoise correction isn’t available in a fully-automatic way for the gradient and Hessian. Or is it?
It works for gradients and Hessians, but it’s turned off at the moment as it does not yet interact with optimize or frequency.