I’m not saying it won’t work unless you do it; otherwise the node software would not pass QA.
I’m saying that due to the nature of QUIC being a protocol on top of another protocol, that therefore has no idea about QUIC, and all the network stack it works on does not know about quic, quic has to do a lot of work to figure how how and where to route packets. The fewer challenges you present to it the higher chances of it working. Swiss cheese model - Wikipedia.
Having multiple interfaces and multiple forwards are evidently enough on some platforms to derail it.
Obviously, if it works for you repeatedly and reliably – don’t change anything. But this topic contains “QUIC Misconfigured” wording. So it does not work reliably. And therefore, giving QUCK best chances is a way to go.