"shouldn't" is ambiguous as it might suggest the responsibility is with the the user of eBPF rather than internal to it.
Perhaps "is designed not to" but that's a mouthful.
I think we should accept "can't" and yet know the limitations of certainty.
If there's a physical possibility, it's just a matter of time before someone finds a way, as was proved by the CPU cache bugs leaking information.