Yeah, that fixes it, though I feel like this should still be considered a bug (considering it does literally cause a visual bug) especially because the default SignalBehavior is what causes this to occur.
If there aren’t any plans to fix this directly, it would be nice to have some sort of studio-only warning that emits in situations like this, or something along those lines.