UWP has native C++ APIs. So does Win32, right?
https://docs.microsoft.com/en-us/cpp/windows/universal-windo...
https://www.google.com/amp/s/kennykerr.ca/2019/01/25/the-sta...
On the other hand, you do require C++ for DirectX.
Android J++ as Java fork could pretty much use something else other than JNI, after all they are using another VM to start with.
Second, even with JNI, there is a big difference between forcing millions of developers to write boilerplate by hand, and offering an Android Studio based tool that would automate the grunt part of the work.
Finally, update yourself with the Java world, Oracle is indeed bringing forward a JNI replacement.
http://openjdk.java.net/projects/panama/
Which, naturally will never arrive to Android J++, but that is a discussion for another day.
The point is not having to deal with Java, one my favourite languages.
The point is the whole experience of how the NDK lacks debugging features, how after 10 years one still has to manually write JNI boilerplate by hand without any kind of binding generator integrated in Android Studio or better given Dalvik/ART why not something like gcj's CNI, how Gradle still isn't able to properly handle NDK dependencies in AAR files, how the ISO C/C++ libs still aren't fully ISO compliant.
And lets not forget some Android APIs, like Vulkan, real time audio and ML are NDK only, so eventually one needs to deal with these issues anyway.
It is also not possible to use C++ to fully write iOS or UWP applications, yet there is a much more productive and developer friendly integration between the managed layer and the bottom parts.