[Bug] v2rayNG 2.3.8 / libXray 26.9.9 breaks Hysteria2 mport UDP port hopping

v2rayNG 2.3.8 / Xray 26.9.9: broken
v2rayNG 2.3.7 / Xray 26.7.28: works
Hysteria2 + Salamander
mport=20000-20500
hop interval: 30s
Actual behavior:
With v2rayNG 2.3.8, server-side tcpdump shows all HY2 traffic going only to UDP/443. No packets arrive on UDP 20000–20500.
Expected behavior:
Client should periodically switch destination UDP ports inside 20000–20500.
Regression test:
Downgrading only the server to Xray 26.7.28 did not restore hopping.
Downgrading the Android client from v2rayNG 2.3.8 to 2.3.7 restored UDP port hopping immediately.
tcpdump evidence after downgrade:
destination ports changed, for example:
20483 → 20435 → 20189
Relevant release change:
libXray 26.9.9 release notes mention removal of obsolete QUIC udpHop handling.

mport=20000-20500 is still successfully parsed/imported by the client, but the actual outbound traffic remains on UDP/443.
mport=20000-20500 is present in theimported URI / config on both

versions.

The issue is reproducible with thesame server configuration and sameHY2 credentials.

Reproduce with v2rayNG 2.3.8/libXray 26.9.9 and a Hysteria2 Salamander config using mport=20000-20500, then compare behavior with v2rayNG 2.3.7. Start by reading the libXray 26.9.9 release note about removing obsolete QUIC udpHop handling and the client import/config path for mport. Done means tcpdump shows HY2 traffic hopping within UDP 20000-20500 instead of staying on UDP/443.

Do mô hình lập chỉ mục viết ra từ nội dung của issue.