Oops, you are right. I think because the other direction of libffi - ffi_closure - has a jitted trampoline, I mistakenly thought both directions are jitted. Thanks for the correction.
And the JITting in closures amounts to a total of three instructions; certainly not for speed, rather just as the bare minimum to generate distinct function pointers at runtime.
