Move your hand object based on the Leap hand position. Set the shape position and orientation using the bone position and rotations in the Leap hand. You might not have to send the bone positions and simply use the rotations -- it probably depends on how your hands are set up.
I would get this working on a second set of hands in the same scene before I moved on to driving hands in a remote scene.
Figure on about 3-4k of data per hand per frame, If you ran at the Leap Motion frame rate, that could saturate your bluetooth channel. You might consider running the "remote" hands at something closer to 30fps than 110fps.
On Windows, Unity uses Visual Studio as its editor. As far as the Leap Motion is concerned, it is more of a matter of compiler support rather than IDE support. You should be able to use any C# Bluetooth library on the PC side. There are a few on the Unity asset store (not necessarily free). I/m not sure how it would work on the Android side.