You still need to be able to plug in stuff like decorators to say, invert values, have a throttle or a counter and etc.
Essentially you're going to need a wrapper to create a tree from either a DSL or e.g JSON from a GUI.
A behaviour tree can be data-driven easily, which opens opportunities for easy editing via DSLs, graphical tools and even changing the AI on the fly at runtime. If you can afford it, do BTs.
If you're using a language that has either lightweight threads or async/await built in, would you still use a behavior tree, or would you just write code?