Although Xeon Phi (formerly Larrabee) has grown to have full-blown x86-64 cores, it's not as easy as plugging the card in your system and suddenly having 60 more CPU cores to play with. There are multiple issues a programmer has to deal with: asymmetric memory access, different instruction sets supported by the main processor and by the Xeon Phi cores and few others. The biggest issue is that Xeon Phi doesn't add more processors to your box, it is actually a standalone computer running Linux (which can share memory with the host computer).
Corona would have to run on Linux to be able to run on Xeon Phi. And in the end it probably wouldn't be much different from having a standalone powerful multicore machine used for distributed rendering.
There are few more implementation issues. There are 60 cores running at around 1.3 GHz, but each core is running 4 threads in parallel. So you actually have 240 threads, each running at 325 MHz. It can be a bit difficult for programmer to effectively juggle this many threads. Also to effectively use the available performance, Corona would have to be adapted to utilize the 512-bit AVX3/AVX-512 instruction set (a subset of which is also supported by the new Skylake Xeon processors).
Don't get me wrong, I would love to get my hands on this Intel beast and have an opportunity to play with it and bend Corona to its will. But I also believe that there are still many more other optimization opportunities which will benefit all users (there are not that many who can afford to buy Xeon Phi).