In reality, this will take a bunch of time to actually show much real results. We've been producing async future driven libraries for a long time, and they're generally pretty good at keeping the computer busy while sending out many concurrent IO requests. The real benefits are when these libraries start to support these virtual threads which should ideally lead to less complexity and some lesser compute overhead (my hopes).
I imagine a lot of the missing structured concurrency will get built up over time on the Java side, but it is an interesting talk regardless.
As a developer if you're targeting the JVM with virtual threads you may decide to use those for some workloads instead of coroutines.
In the future when targeting the JVM Kotlin maybe can use the features exposed by Project Loom to execute coroutines more efficiently, but it's not clear to me that there's much for Kotlin to gain there, maybe some small gains in performance.
And since they also want to compete with Swift and TypeScript, on their own turf, even less likely.
This is the thing with guest languages, cannot embrace the platform, always full of compromises.