Force SNMP Traps to LAN over VPN

I have a FusionHub on AWS and several B One Routers at locations to allow for multiple clients to report back to an AWS hosted monitoring software. Part of this the receiving of SNMP Traps from end points. At one site there is a conflict as the IP of the AWS hosted monitoring software is in the range of the local network. I have been looking for a way to send the SNMP Traps of the End Points (not direct clients of the B One, but a hop away) to the LAN side of the B ONE then based on port or protocol send the SNMP traps across the PepVPN and to the FusionHub and finally the monitoring software.

I have been attempting to use Custom Service Forwarding with no success. The end points will not have access to the WAN side so LAN is my only option. Before I go and start making changes on the AWS side or building a new VPC just for one site; Is there a service or that I am missing or setup in the Service Forwarding that allows for the rerouting of incoming data to the LAN side to be re-routed across the VPN?

Use virtual network mapping at the remote site so the subnets don’t overlap?

I completely agree. Unfortunately with the red tape at the remote site that would take at least 6 months. Hence why I was looking for a solution in the B One itself. But it is what it is and I may just have to add an new FusionHub and monitoring software in a separate VPC for this site and possibly future sites.