IMO there are cases where a Swift wrapper is beneficial. Things like suspend/async functions, enums and interface/protocol extensions for example. However generally speaking I wouldn't just wrap everything in a Swift type.
Once you encounter a limitation in the Kotlin - ObjC - Swift interop you just need to asks yourself if it's that big of an issue. Depending on how big of an issue it is you might be able to live with it, tweak it on the Kotlin side, or as a last resort use some Swift magic.