That's a big if. In practice you're not going to be able to escape needing to interface with Java code others have written. What then? You either waste time putting up shims in front of every single API or, more likely, give up and just go with it, at which point you've lost.

It is much more practical to choose a language that does not have a terrible history of poor API design to begin with.

There are plenty of good libraries that don't suck you into a hellscape of frameworks or enterprise java

What language that's been around for long enough to have a large ecosystem doesn't have a terrible history of poor api design?

But sure, if you pick a really new language, you do get the chance to be that history for future generations