The future of Swift Export is unknown, and whether it replaces SKIE or not depends on how far JB will go with it. Kotlin and Swift are fundamentally different languages so opinionated decisions have to be made to make the interop better, which is something we've done with SKIE.
The issue with not being able to use ObjectiveC export along with Swift export is that it's all or nothing. If you have existing Swift code that uses current KMP (ObjectiveC export), then you may have breaking changes. Also Swift export still doesn't support every Kotlin declaration type, so it can't replace ObjectiveC export just yet.
Also, ObjectiveC export is not bad, especially when you use SKIE which smooths the interop for stuff that's not available in ObjectiveC. Honestly if I was to decide between using Swift export without SKIE or ObjectiveC with SKIE, it'd go with ObjC export + SKIE at least in the foreseeable future.