I think the pathfinding obstacle will always cause issues.
However, I remember a similar question to this a while back for Triarite on the discord.
The recommended solution there was just do an event checking for the furthest away from the pathfinding target, then setting the speed to 0.
“pathfindingobjectname is in collision with pathfindingobjectname” and “Pick the pathfindingobjectname nearest to targetdestinationX;targetdestinationY (Inverted)”
Then just set the speed to 0 as the action. It’ll stop moving until it’s no longer in collision.
You can try this in the pathfinding AI example with the following setup:
