Not really sure what your network architecture looks like, it’s a bit hard to follow. But, why wouldn’t you just create another non-Meraki site-to-site peer on the existing MX for the AWS connection?
If you’re trying to do two separate VPN connections into AWS then it might actually be worth looking at your VPC design and introducing a transit VPC that acts as a bridge-head, so you still just have the one VPN to AWS and then forward traffic from there - might also be worth considering the vMX.
Also, it’s hard to understand what the “breakout load balancer” is. Is this just load-balancing between WAN1 and WAN2 on the same MX? If so, then that’s an ‘interesting’ configuration. If the load-balancer is being used to ‘split’ the connection between an active and standby unit in a HA pair then I understand.