>So, your conspiracy needs to involve the Certificate Authority (Let's Encrypt in this case), the CT logging team at Google...
No, as you alluded to, my conspiracy only needs that the user uses any of the many browsers besides chrome.
No, as you alluded to, my conspiracy only needs that the user uses any of the many browsers besides chrome.
The SCTs can only be produced by these logs, and only when the log is shown the tbsCertificate data. The intent is that the log service promises to log all certificates for which it provides a timestamp. A Merkle Tree is used so that we can examine a log and obtain proof that it does indeed contain every certificate we've seen SCTs for.
So, your conspiracy needs to involve the Certificate Authority (Let's Encrypt in this case), the CT logging team at Google, and at least one third party log operator. Or it would be detected when it was tried.