People will try to use systemtap for hot-patching and other uses for which it is not intended. We should consider tainting the kernel, or at least writing entries to the system log when programs that modify system variables or structures run.
The translator could emit a call to "printk(...); add_taint(...);" during module initialization for any probe script that includes $target variable writes. I don't see an existing TAINT flag that would be a perfect match, the closest being TAINT_FORCED_MODULE.
We printk during module initialization for all systemtap scripts.