I think it depends on what you're trying to build.
I was working on a 'toy app' earlier this year. I needed to use MapKit, but the SwiftUI MapKit is pretty simple, features-wise.
So I had to do the more complicated (relatively-speaking as someone with no prior UIKit/Swift experience) solution of using a UIViewRepresentable to host a UIKit MapView.
It wasn't the hardest thing to implement but it definitely shows that SwiftUI can't handle everything.
I definitely think having that 1:1 parity will help and hopefully it doesn't took too long.
I was working on a 'toy app' earlier this year. I needed to use MapKit, but the SwiftUI MapKit is pretty simple, features-wise.
So I had to do the more complicated (relatively-speaking as someone with no prior UIKit/Swift experience) solution of using a UIViewRepresentable to host a UIKit MapView.
It wasn't the hardest thing to implement but it definitely shows that SwiftUI can't handle everything.
I definitely think having that 1:1 parity will help and hopefully it doesn't took too long.