QUIC has something which can help with that (from https://tools.ietf.org/html/draft-ietf-quic-transport-09):
"QUIC connections are identified by a Connection ID, a 64-bit unsigned number randomly generated by the server. QUIC's consistent connection ID allows connections to survive changes to the client's IP and port, such as those caused by NAT rebindings or by the client changing network connectivity to a new address."
If that's not enough for your use cases, now is a good opportunity to mention them and suggest enhancements, since the IETF standard is still under development.
Sure you could use another port, but it looks like UDP 443 is becoming the unofficial standard, even if not IETF endorsed...
But it makes perfect sense to have a defined port, so that connection racing can work without first having to receive a HTTP header
As for classifying existing Quic connections, it might get a little messier. There are still some cleartext fields but it might require observing multiple packets in the flow before making a guess the traffic is likely to be Quic.
Meanwhile an explicit design goal of Quic is to avoid interference from middleboxes, so it would be no surprise if a perfect iptables Quic match is or remains impossible.