Hi Tyler,
It's a good thing to use the HTTPS version of the badge on your HTTPS pages because otherwise, the page would be reported as unsecure by the browser to the user.
On the other hand, displaying HTTPS ressources on a HTTP page matters. Downloading and decrypting the secured ressources will use more bandwidth and CPU on the server and client side. In other words, HTTPS is slimply slower than HTTP so it will be detrimental to the user experience.
The difference might not be signigicant, but it's always good to keep that in mind. So, I simply suggest you match the protocol of the ressources with the one of the requested URL. HTTPS with HTTPS and HTTP with HTTP.
Best regards,
Guillaume Voyer.
