My understanding is that Chrome only cares about this sort of thing when it's a CA in the default trust store that shouldn't be impersonating them. User-added certs like in your example are fine, because explicit action was taken.

See Adam Langley's blog about this here: https://www.imperialviolet.org/2011/05/04/pinning.html