Cool project! In the early days of thinking about how to support SVG in Compose, converting them to composables was an approach we considered. One of the benefits is that they become very easy to parameterize and can support arbitrary behaviors (ie. once the SVG is in Kotlin, you have the full power of Kotlin available). The downside was that designers work with SVG files, and when they make a change to the graphic, merging that back into modified Kotlin code is messy. If the argument is that the Kotlin code should never be modified, then the question becomes "well why didn't you just load the vector graphic from the SVG file then?".
Anyway, food for thought. I wonder if a path of less resistance might be to contribute a change that adds support in Compose Desktop. Compose is open source, after all, and most of the loading code is already there in aosp for Android.