Given that Core is never CPU constrained, this cost does not show up on the wall clock for them at all. But bip324 was promoted as performance neutral and even performance positive due to the removal of the sha256 checksum. That could have been removed without the privacy/encryption - so isn't a genuine argument. But this also ignores the effects of native sha on the checksum computation. On machines with native sha, the checksum is basically free and the encryption therefore is significantly more costly.
"Each v1 P2P message uses a double-SHA256 checksum truncated to 4 bytes. Roughly the same amount of computation power is required for encrypting and authenticating a v2 P2P message as proposed."
(edited)