As to "bringing nothing new to the table at all", I'm not sure about that. It depends on your definition of "nothing" and "something". I think they certainly bring convenience, and their[1] switching costs are orders of magnitude lower compared with Scala's. The question is, then, is the "something new" Scala brings worth the price. Again, the answer to that depends on the user. Some will think it most certainly is; others will find the cost way too high.
[1]: Well, Kotlin's; not Ceylon's
As a straight and immediate Java replacement, I'd definitely recommend Kotlin as well. If you want to switch over existing Spring apps, you will not get the best out of Scala. Scala, in my experience, is most effective when written without Java goggles on. But Scala definitely has large advantages for new projects or broad refactorings.
How so? Scala may have more ways for features to interact and I guess a larger library ecosystem to become aware of (though it seems perverse to count a large library ecosystem as a downside), but IME most of the cost of switching is in tooling support and finding a developer community to answer questions - both areas where Scala is far ahead of something like Kotlin.
Ceylon and Kotlin grab the low-hanging fruit. They are better Javas. These languages bring nothing new to the table at all. They will actually suffer from Java 8, because Java 8 itself is a better Java like they are. People write Kotlin and Ceylon because they need to write a Java app but they don't want to write Java.
Scala is not meant to be a better Java. It can be used in that way, but it's not meant to be. It has a vastly richer set of features, probably one of the most sophisticated type systems of any language, and a growing number of Scala-specific libraries. In addition to people writing Scala because they don't want to write Java, there exist many people that want to write Scala because of Scala.
The same general argument seems to apply to Clojure. Just because your language runs on the JVM doesn't mean it's just an alternative for Java.
(This is not to say that I don't think Kotlin at least is shaping up to be a beautiful language.)