Doesn't matter, at some point there's a indirect function call and the compiler can try to guess the target, inline it and add an address check that, on failure falls back to the slow path.
This actually seems like it’d be quite beneficial, as I’d assume 90+% of method call targets can be statically guessed just by looking at the code (to increase this ratio even more, I’m sure Apple could even ignore Cocoa methods that use the forwarding machinery).