Should work OK, I think I did this a year or so ago for a customer. The main thing is routing, so make sure the route for the remote 3030 network points out the same interface as where the hosts are. The router theoretically should be able to figure it out OK.
Trouble is the return traffic from the local hosts needs to go to this VPN router, not out to the Internet (assuming this is a different router or these hosts are already on the Internet, the hosts may have their default gateway set to a different device than this router). You may need to add a static route on each device telling it how to get to the remote 3030 network via this router. Even after doing that, this router will receive the packet from the host, see that it has to send it back out the same interface (albeit encrypted), and will probably send an ICMP redirect to the originating host to tell it to send all its packet straight to the other gateway from now on. This will obviously break your IPSec tunnel. Putting "no ip redirects" on the crypto interface should stop that.
In short, it should work but you need to make sure routing is working, pay particular attention to the local hosts.
Table of ContentsIntroductionVersion HistoryPossible Future
UpdatesDocuments PurposeNAT Operation in ASA 8.3+ SectionsRule Types
Network Object NATTwice NAT / Manual NATRule Types used per SectionNAT
Types used with Twice NAT / Manual NAT and Network Obje...
Table of Contents Introduction:This document describes details on how
NAT-T works. Background: ESP encrypts all critical information,
encapsulating the entire inner TCP/UDP datagram within an ESP header.
ESP is an IP protocol in the same sense that TCP an...