I understand your view, and yes if only applicable to an access interface, and not tagged/trunk, then addition of VLAN makes little to no sense as a requirement - could somehow be related to the implementation, I guess.
I assume you think access only from this statement:
MAC limiting sets a limit on the number of MAC addresses that can be learned dynamically on a single Layer 2 access interface or on all the Layer 2 access interfaces on the services gateway.
I would NOT trust that the use of the word Access above equates to true Access port, versus any port. I would "think' that if not supported on L2 tagged/trunk interface (where VLAN would then matter for sure) that some NOTE saying so might be present, but who knows???
i think best to just accept VLAN needed in the command structure and leave it as that, . . .