This is a "writing code"-centric point of view. From the maintenance perspective "you" aren't the only person for whom the tradeoffs of callbacks/promises/async-await matter. It also matters to the people who have to come along years later and maintain the software.
So really it's about what abstraction makes sense for the maintainers as well. Not just you.
> people who have to come along years later and maintain
The problem is there is no way to know years in advance what makes sense for those future people. All you have is current standard at your org and/or common sense. Do what they say.
When you choose what the standard is, select whichever makes more sense at the moment. That is kind of my original point.
You may not know their own personal preference when writing code. But you can know what will make their job easier. Strong typing for instance will make refactoring easier. Good perf tooling will make analyzing performance easier and so on.
So really it's about what abstraction makes sense for the maintainers as well. Not just you.