Scrolling like it's 2008: SwiftUI and Jetpack Compose
skip.tools
skip.tools
I can't speak for iOS, but neither RecyclerView nor Compose's scrolling is built on top of the Android platform's scrolling - they both implemented new and different ways to do scrolling versus the ScrollView or ListView the platform shipped with. Both were built using the same public APIs any developer could use.
The reason they offer the performance they do is implementation choices by the developers who wrote them, around what work to perform when. Lots of Android developers implemented scrolling using the platform APIs and got jank, others implemented scrolling before RecyclerView was even available and had smooth performance. There is no magic performance guarantee because you transpile to kotlin.
There are two parts - that you can run SwiftUI on Android, and that you can run your Swift business logic & data on Android. You don't have to use the former to benefit from the latter per your concerns
In 2025 it's very common to have common cores and per-platform UI, such as with Rust (which popular apps like Brave and Anki do). This is one way to do so, plus optionally (not necessarily!) using SwiftUI on Android. I don't think you can go to the Brave or Anki open source projects and tell them they would save time by deconstructing their Rust cores into platform-specific redundancies without being laughed out of the room.
(I have no affiliation)