I totally agree with Shawn. First step is to get your project working on a newer Kotlin, and get rid of that tech debt. Then consider adding new technology. As the new technology will potentially introduce it's own issues, and you won't know if it's the old, or the new.
And often the 'solution' is to upgrade something, so if you can't upgrade, you could end up in a Catch-22...