MultipeerConnectivity provides abstraction away from infrastructure Wi-Fi, P2P, and Bluetooth. This means that your devices will communicate with each other however they are capable.
If you can connect two devices over Bluetooth then they can also be connected over infrastructure wifi assuming they're on the same LAN with no restrictions (so if you're at a large corporation you might have some issue with this because of IT).
MPC allows you to communicate with multiple devices connected via entirely different transports. So if A, B, and C are all devices that can be discovered and connected using the UUID you specified, A only has bluetooth on, B has bluetooth and wifi, and C has only wifi on, then A will automatically be able to receive messages from C because B is responsible for completing the ring.
All of this functionality is provided by MultipeerConnectivity already.
For a walkthrough of how to properly discover, connect, and communicate with peers check out the wwdc video "Nearby Networking with Multipeer Connectivity" here