@upretirementman: Leap with Python 3.3 per se is something that users have been able to do by following this article. Leap with Python 3.3 inside Blender is even something that has worked okay for users on Windows and Linux. For OS X which has been more problematic, I've posted a special build of Blender in your other thread.
Your UDP socket-based solution to communicate between Python 2 and Python 3 was also viable. I saw your video apparently demonstrating that approach.
@shadowmint's solution with ctypes is pretty awesome. It avoids having to create a new LeapPython.so across Python 2.6, 3.3; avoids having to use install_name_tool to switch between python.org Python, OS X-included Python, MacPorts Python, Homebrew Python; allows use of pyinstaller; and most notably here provides compatibility with a prebuilt OS X Blender app despite its statically embedded Python.
@upretirementman: As for your last error, cleap is a directory as you can see on the Github link. The easiest thing to do would be to place a copy of that folder adjacent to bleap.py or whatever source file is trying to import cleap.
So now you have at least a few options for how to use the Leap API inside Blender.