That would be lying though, and it could get you in to a whole pile of hot water. Such 'technical tricks' may work a few times but eventually you'll have a real problem.
What do I call that solution? "Developed in Java". Here Rhino is to Java what JavaScript is to a HTML web site.
Stuff like that tends to have consequences, especially when there are contracts and liabilities involved.
Also, if you're hiring programmers who can't pick up a new language to work on your project, you're doing it wrong. Most of the capable folks I've worked with loved learning new tech; the problem is usually keeping them from jumping onto a new platform for every project.
Clojure is 100% compatible with Java, both ways in a straightforward manner, so you can easily argue that it's still Java. That's been the smartest design decision ever by its designer.
You have to understand whether your clients are interested either in leveraging the Java technology or employing code-drones. In the former case, Clojure will be fine; in the latter one it will not.
Popular wisdom teaches that most people remember the result, not the way you got it. If you use Clojure and succeed, you'll have your own way.