No, loading the certificate to display that error in the first place does involve making a connection to the site. The risk of getting malware via that process is nearly 0, but the website certainly could see the initial connection.
Blocking malware domains at the DNS level and enabling Safe Browsing in your browser are both things which could prevent this from happening.