The OCSP Responder is the same webserver and it is not accessible from the internet.
OCSP don't need to be externally accessible, only IIS server needs to access internal OCSP server. IIS queries OCSP and gets OCSP response of its TLS certificate. Then, when remote client initiates TLS connection to IIS, it will staple this OCSP response in TLS handshake and clients may use this stapled OCSP response to validate certificate revocation status. OCSP stapling on IIS is enabled by default.
I guess just opening a certificate in MMC will not trigger a revocation check...?
yes, that's correct. Revocation checking isn't triggered when you open certificate from file or MMC.