This is an expected behavior, as the LACP negotiation cannot complete until both ends (ESXi and physical switch) are properly configured.
VMware vCenter Server 8.X
VMware vSphere ESXi 8.X
This behavior is caused by the fact that vCenter has no visibility into the physical switch's LACP configuration, specifically, whether multiple ports have been properly bound into a channel group. Thus, the value set for the advance setting parameter TeamPolicyUpdelay is triggered and the delay is expected.
It's important to note that this timer is not applied during the initial LAG creation, such as during host reboot, but takes effect for subsequent LAG operations (e.g., reconfiguration or uplink changes).
This is expected behavior.