Hi Jeff,
For a true air-gapped VCF environment, I would go with option 1 and maintain an internal/offline depot rather than manually importing each ESXi update into vCenter.
Broadcom provides a supported VCF Offline Depot workflow specifically for disconnected environments. For VCF 5.2+, you can configure it under SDDC Manager → Lifecycle Management → Depot Settings → Set up an Offline Depot.
This gives you a more repeatable lifecycle process and avoids manually moving individual bundles for every update. You can also point vCenter Lifecycle Manager to the offline UMDS repository and synchronize the ESXi image metadata/vendor add-ons from there.
For option 2, manually importing the ESXi offline bundle and Dell vendor add-on into vLCM is supported for isolated vCenter environments, but I would use it more as a targeted/manual approach rather than the primary lifecycle strategy for VCF.
So you aren't missing anything major with option 2, but for VCF I would prefer the Offline Depot approach because it keeps lifecycle management centralized and repeatable.