As it's clear in this line: https://github.com/magazino/move_base_flex/blob/9c5fb1b47b94a32d575b5544466fb4d15450c8f7/mbf_abstract_nav/src/abstract_controller_execution.cpp#L462 the robot wouldn't stop after aborting from the exe_path action, which is very problematic when there is no watchdog to stop the robot if it doesn't receive any new cmd_vel.
Also with the current implementation, the name of the stopMoving doesn't make sense, because it doesn't really do what it can be inferred from its name. I also understand the point of commenting out this line and it can be useful, but I would separate the implementation of these two cases.