On behalf of the client, not the server.
Answers:
When you set up an IPSEC policy on a VPN tunnel, it's for a specific IP gamut. Any traffic that falls into the length should walk through the tunnel unless it have be more specifically predetermined within the VPN setup.
Unless you own some other channel to route the traffic to that same host that you've created a VPN for, here should be no track to go past the traffic to them except beside the IPSEC nouns.
By outlook of VPN and IPSEC usage, it's unlikely that here's any other path to connect to that target host EXCEPT through the tunnel.
In most devices, in attendance's the IKE segment of the tunnel setup, consequently the IPSEC policies that control the traffic flow (and associated IP ranges) and minus them, the traffic won't walk through.
Hope that help.
If you can update near some more specific examples of the traffic and where on earth it's head (IP address, etc), or how you picture it could seize near minus going through the IPSEC tunnel, perchance a more specific answer can be formulated.