We don't offer VPC-VPC connectivity, but if the main concern is latency and/or network path the traffic takes - we've experimented with this across AWS accounts, and we've seen that the latency between EC2 instances running in different AWS accounts in the same region, is identical to the network latency when those EC2 instances are running in the same AWS account in the same subnet.
So the physical path that traffic between EC2 instances running across the AWS network in the same region is the same, regardless of whether it goes out via a public IP (owned by AWS) and comes back in to the AWS network, or if it just uses private IPs inside a VPC.
This is because AWS adds a software defined network on top of the physical network to segregate accounts, VPCs, etc. And it's able to tell when a public IP is part of the AWS network and routes that traffic straight back into the same data center(s).