I am sorry, I do have a direct answer to your question, nor the possibility to test it myself right now. If I had to give an educated guess, I would say that inter-profile isolation will prevent this communication.
That been said, you can test it yourself very easily.
The basic concept is to install on a profile something that will open the socks5 proxy, like ssh in termux, orbot, etc..
On the other profile you can use another app that can use a proxy, like proxychains/nc/curl in termux or an app that supports orbot OpenKeyChain, Conversations, etc..
If the connection goes through, you tested the isolation yourself.
This way you can decide to make the test with meaningless data and avoid giving out important information.
If you really don't want to land on Internet for this test, you can use this setup:
On one profile you have a nc (in termux) listening on localhost and a socks5 proxy set with ssh.
On the other profile you try to leverage the proxy to reach the nc listening on localhost (for example with another nc in termux).
I don't know if there is a faster/smarter way to test it, this is most probably what I would do if I had to test it now.