Current Kotlin/Native based Wasm target prototype has form of reference counting, but it is moving away from it:
https://blog.jetbrains.com/kotlin/2020/07/kotlin-native-memory-management-roadmap/
I’m not familiar with Perceus, but skimming the paper, they seems to have an open issue with cycle collection, which would need to be solved to be used in language like Kotlin, where you can freely form reference cycles without weak references.
In Kotlin/Wasm we want to use GC of JS engines (instead of custom GC like Perceus) to simplify collecting cycles between Wasm, JS and DOM tree.