Why does my USG200 take the wrong route to the other network

Hello,
I have some troubles with routing traffic between 2 networks. A bit context may be required to understand my situation. I'm joined a company where i'm fully responsable for everything which comes to IT as the previous employee left. As the network is old fashioned and out dated (hardware, software and configuration) we decided upgrade the whole network by replacing it with a new one. To avoid that i need to do a "big bang" i will create the new network in parallel to the current/old one. The idea is that the old and the new network are connected/routed to each other so devices in the new network can reach devices in the old network and visa. We have 2 WAN connections in the building so each network gets its own WAN connection until the migration is finished. I made a sketch about the situation i already build including which connections are working and which connections don't. When i login to my USG200 CLI and do a tracepath to 192.168.222.2, this is the result:


I created a route policy on the Zyxel USG200:

And a static route (which i suppose should not be required as the route policy covers this route but with the route policy only i have the same problem):

When i do a tracepath from the USG200 to 192.168.222.2 or 10.128.10.1, this are the results:



1. ---------------------------
When i understand this correctly, the route to 192.168.222.2 looks correct but the route to 10.x is routed to the public IP, so WAN. I do not understand why this happens as i configured a static route and route policy for the 10.x network.

2. ---------------------------
Another thing is when i ping 192.168.222.2 i would expect that i got a response (as pfSense allowes ICMP on the 192.168.222.2 interface) but i got this