No, of course most people don’t notice, because they don’t chain moves by waiting until the move stops before setting the next one. And even if they did, the Animation Blueprint usually has blends between various modes of animation, so you’re not going to see a big single frame transition into a stopped movement animation, you’ll see a smooth transition between two different movement animations (or if the same one, then it’ll blend out and right back in with no visible difference)
Just because you think something should behave differently than it does, does not mean it is a bug. Behavior Tree is not “very bugged”, in any way that I’m aware of (it might well be in ways I’m not, I guess, but for the most part, once you understand how it works, it does what it does quite well).
It is not a bug that velocity is 0 when you reach the end of a move. That’s the definition of the end of a move.
If you want it to act differently, you have different requirements than what Epic has, and you have the tools to implement it.
What specifically is the problem you are getting with a frame at zero velocity? (although honestly, i’d have to write a test to see if the velocity actually is zero, because if in the same frame your moveto ends, you set a new destination, it’s going to do that after the velocity is zeroed, so the new move should have a velocity)