How good is the idea to use behavior tree for player movement?

I develop a game with Unity. Now I implement a player parkour (movement) system, so I try to choose pattern that will help me to keep architecture clean in the long term and easily add new states. I tried to use state machine pattern, but I realized, that it grows more and more.

So I gave up on this solution and decided to use behavior tree pattern. But now I'm starting to notice, that this architecture is going deeper and deeper and conditions for parallel states become difficult to control. I think this is not a best way to create player parkour (movement) system.

So my question is: is there a better way to create player movement system and how hard will it be to work with the behavior tree? Maybe there are pitfalls in behavior tree that I didn't notice? I'm searching for architecture, that let me perform parallel states (or analog) by conditions and will be easily maintained.

My prototype now looks like this (don't pay attention to get keys, it's just a quick plan for architecture):