Sure -- feel free to pick any Activity and convert it to Jetpack Compose at your own leisure (our team is not planning to start migrating to Compose any time soon), and we'll evaluate how beneficial it would be to migrate other things to it.
However, I would prefer it to be a nontrivial activity (something that uses network calls, custom Views, etc), so that all the benefits, as well as caveats and shortcomings, of Compose can be apparent. Something medium-sized like LanguagesListActivity or RandomActivity/RandomFragment or WiktionaryDialog and so on.
Also please be advised that the converted Activity should have the exact same behavior, functionality, and design elements as before conversion.