Rakudo's had more testing since it's been around forever but MoarVM is where my hopes lie. Here's hoping user adoption isn't fractured that badly like D's Tango vs Phobos debacle (which only now it's recovering from, I'd argue largely due to Andrei Alexandrescu's charismatic persona, haha.) Perl 6 is a really interesting language and I'd encourage you all to play with it, but it's an entirely different beast than Perl 5. They should have just renamed it entirely.
Is that wrong? If not, did you mean "Rakudo on Parrot" or "Rakudo on the JVM" when you wrote just "Rakudo"?
It's like this: Rakudo -> NQP -> MoarVM
or like this: Rakudo -> NQP -> NQP-JVM implementation -> JVM
Want to get Perl 6 running on the .Net CLR? Implement an NQP interpreter (which is supposed to be fairly easy) and you're 99% done (at least that's my understanding).
Sure, MoarVM is by design semantically close to NQP, but if you look at
$ nqp-m --stagestats -e ''
Stage start : 0.000
Stage parse : 0.003
Stage ast : 0.000
Stage optimize : 0.000
Stage mast : 0.005
Stage mbc : 0.000
Stage moar : 0.000
you get mostly the same steps as on the JVM $ nqp-j --stagestats -e ''
Stage start : 0.000
Stage classname : 0.045
Stage parse : 0.067
Stage ast : 0.000
Stage optimize : 0.009
Stage jast : 0.145
Stage classfile : 0.010
Stage jar : 0.000
Stage jvm : 0.003
except that MoarVM bytecode files do not get bundled into JARs and there's no need to do the extra processing that happens in the 'classname' stage.