How did you determine that these are all the command that are needed here? There also is a AICMD_ATTACKFOLLOW_WAYPOINT_PATH and it is not obvious whether that needs covering as well.

I wanted to match the same values as commandRequiresAmmo and isGuardCommand from #1757.

I had originally added the waypoint path values but I ultimately deemed them unnecessary as they're scripted events and such events typically involve carefully managed specific behaviours. I'm happy to add them back if you think it's worthwhile adding them anyway.

How did you conclude they are scripted events? Wouldn't all AI command be subject to use in scripted events?

By observing script actions for them in the World Builder and looking at the code paths for those behavioural states.

For starters, I've only ever seen AIFollowWaypointPathState entered via scripted events as it pertains to pre-existing waypoint paths placed on the map.

There's also seemingly no way to achieve aggressive waypoint path behaviour with player-controlled units. Look at how aiAttackFollowWaypointPath and aiAttackFollowWaypointPathAsTeam are called via AIFollowWaypointPathState::update - they rely on the AI state's mood matrix to return MAA_Action_To_AttackMove, which is not possible when the MM_Controller_Player bit is set.