"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.