I played with something similar. If they start with events, you could disconnect the execution pin. Or do it with custom events (treat them like functions, swap in and out as needed).
If code isn’t triggered, it’s not executed. It may or may not be compiled into the blueprint, but it won’t run if the path of execution never goes through one of those white lines.