processBypass() could do that, but for that example, I’d just leave it unimplemented since users would most expect silence. Think of bypassing as disabling. When you stomp on a guitar pedal to turn it off, it routes inputs to outputs. When you turn off a mixer, it outputs silence.
An example of when you’d override processBypass() is if your module has alternate modes/firmwares with different routing.