>it doesn't lend itself to reuse, but I don't blame it either: it's not really meant to do that.

Only if you keep writing more logic into build.gradle.kts.

Writing custom Gradle plugins has been the standard and recommended way to configure your projects for years now. Aside from a few footguns (lol extensions not being resolved at configuration time and needing providers everywhere), it allows you to mostly skip configuration steps.