The answer is simple: no matter which traffic you forward, you still must be able to manage your "IR" server. This is being done via ssh, which is listening on port 22 by default.
The DNAT rule is probably present to avoid traffic for port 22 being matched on the next rule, which changes the destination IP unconditionally to your EU server, no matter which protocol / port is used.
a rule iptables -t nat -A PREROUTING -p tcp --dport 22 -j ACCEPT
would do the same thing (and makes its intention more clear). If you know, that the destination port for v2ray traffic is between 10000 and 29999, this rule can be removed, together with adding those constraints to your DNAT rule.
I am not familiar with the v2ray VPN, and do not know if the protocol to talk to v2ray is tcp or udp - I inserted both to be sure. Based on your description, those rules should do the job:
sysctl net.ipv4.ip_forward=1
# clear all previous rules:
iptables -t nat -F
# add new rules:
iptables -t nat -A PREROUTING -d IR_SERVER_IP -p tcp --dport 10000:19999 -j DNAT --to-destination EU_SERVER_IP1
iptables -t nat -A PREROUTING -d IR_SERVER_IP -p udp --dport 10000:19999 -j DNAT --to-destination EU_SERVER_IP1
iptables -t nat -A PREROUTING -d IR_SERVER_IP -p tcp --dport 20000:29999 -j DNAT --to-destination EU_SERVER_IP2
iptables -t nat -A PREROUTING -d IR_SERVER_IP -p udp --dport 20000:29999 -j DNAT --to-destination EU_SERVER_IP2
iptables -t nat -A POSTROUTING -j MASQUERADE
Again, I do not know v2ray - therefore I am not able to tell if more port-forwarding is required for this setup to work.