Minor nit - inside a given compile object (library, framework, main executable) with PIC all accesses are performed using a pc relative address not a table lookup. The performance impact should be no where near 10%. In fact on arm pc relative addresses are /faster/ as loading an absolute address requires multiple instructions (if nothing else it hurts the icache).

More seriously the use of a offset table is an implementation detail.

On macOS at least dyld directly patches the majority of cross-object calls and accesses through stubs, either converting access to a direct absolute address or a assembly stub that tail calls to the correct place. (Very much a generalization here :) )

So yes if your code is extremely heavily limited by call and load overhead from accessing another library you’ll see a real perf impact. But at that point you should be asking why you’re calling such a lightweight function so much that the call overhead itself is a problem.