From "pure network" point of view, this approach may be viable. Your network looks like IPv4 network for those with IPv4, and like IPv6 network for those with IPv6. As soon as the partners do not need to communicate between themselves. If they do - then having bidirectional communication between IPv4 and IPv6 clouds might get challenging.
But when we look at it overall, including the services - there is more questions. How do partners access the services ? They would use your DNS, right ? And this DNS would need to have the entries for both IPv4 and IPv6 services of yours (A and AAAA resource records).
As soon as the DNS has the AAAA records, those of the partners that have other means of IPv6 access but not the tunnels to your network, will try to IPv6 first - and will in the best case fall back to IPv4 - in the worst case the connections will hang. (What IPv6 addresses do you plan to use ? ULA ? or your own address space ? A lot will depend on that)
So, in short, this idea needs a more thorough analysis which will depend on more details of your setup.