The CA system and hence https/TLS is already backdoored, by construction. Any of root CA’s that your browser trusts can man-in—the-middle you unless you keep track of and pin certificates like Google does. These roots CAs are run by random companies and governments around the world. All of them have equal precedence in browsers.
It’s not that easy. They would also need to MITM the actual traffic, or the DNS.
Same with plain http.
Any fake certificates the malicious CA signs will have to be written to a Certificate Transparency log, which would make noticing the fact that the CA has done something like this easy.
Chrome would need to contact Google servers to send the collected data. Such unexpected traffic would be more easily detectable without IP Protection. With IP Protection, Chrome is sending data to the Google proxy all the time, so it would be harder to detect extra data sent that way.