I haven't thoroughly researched cert pinning, but it seems like basically the same as the SSH message you get when you SSH into a new server. If my understanding is correct, it does nothing to solve this problem.

1. It only prevents you from connecting over a MitM'ed connection if the cert is already pinned, i.e. if you've visited the site before.

2. If your connection is MitM'ed, you have no way to securely access the site you want except connecting over another channel.

I am not sure that works. Putting the MITM certificate in the trusted certificate store will make Chrome allow the interception.