Perhaps by compiling from the bytecode of the existing interpreter, instead writing a whole new source code interpreter for the JVM, it will have some benefits in supporting newer versions of the language. Or, maybe it will help to decouple development of the standard library and the interpreter, possibly letting more devs work on it. You can't really be sure what benefits/deficiencies a different approach will bring until you actually try it - see PyPy, a "silly" idea to implement Python in Python, which now yields faster runtime performance than CPython.
Jython is awesome and all but its fighting an uphill war against rapid progress in 3 with far too few resources.
But it does exist.
https://wiki.openjdk.java.net/display/Graal/Publications+and...
Check "Truffle C: Dynamic Execution of C on the Java Virtual Machine."
PS. Jython also would be called transpiler in modern lingo
To put it another way, Jython makes obvious sense when the primary target is the JVM and there's little legacy code. As target platforms proliferate and the code base becomes cruftier, it may become a less obvious choice.
I'm not sure the Pythonic "only one way" extends quite so far as to make Jython worthy of monopoly status.