> At the very, very least I should be able to pin which CAs I trust so the threat vector doesn't include every CA in the world.
You can do this with CAA records today, to restrict which CAs can issue certificates for your domain.
You can do this with CAA records today, to restrict which CAs can issue certificates for your domain.
No, the browser should check the CAA record and refuse to trust certs issued by the wrong CA.
The idea you're describing has been standardized as DANE, which has failed to gain any adoption. It would not make sense for CAA to try to do the same thing. Instead, it set out to provide a defense-in-depth mechanism for certain CA vulnerabilities that fall short of a full compromise.