Instead of using a standard configuration plan to deploy the configuration, create an auto config plan that uses scripts is what you should do if you want to use NetEdit to manage ArubaOS-CX switches and deploy a standard config to the switches, but need the config to include a few device-specific settings such as hostname and IP address. An auto config plan is a type of plan that allows you to use scripts to customize the configuration for each switch based on variables such as serial number, MAC address, or user-defined parameters1.

Aruba CX 6300 switches are an appropriate choice for leaf switches in a leaf-spine topology that uses Virtual Extensible LAN (VXLAN) with Ethernet VPN (EVPN) is a correct positioning of ArubaOS-CX switches in the data center. The Aruba CX 6300 switches are designed for data center leaf roles, and they support advanced features such as VSX, EVPN, and PFC that enable high performance, scalability, and resiliency for data center networks1

Automated provisioning of LAGs between AHV and VSX is an operation supported when Aruba Fabric Composer (AFC) is integrated with Nutanix. AFC is a tool that provides automation and orchestration for managing data center networks composed of ArubaOS-CX switches. AFC can integrate with various data center software such as VMware vSphere, Nutanix AHV, Microsoft Hyper-V, etc. AFC can discover, monitor, and configure Nutanix AHV clusters and hosts using REST APIs. AFC can also automate the provisioning of LAGs between AHV and VSX by creating VSX LAGs or MC-LAGs on the ArubaOS-CX switches and configuring the corresponding LAGs on the AHV hosts.

ArubaOS-CX is a modern operating system for Aruba switches that provides automation, programmability, and analytics capabilities. The ArubaOS-CX Network Analytics Engine (NAE) is a built-in analytics framework for network assurance and remediation, that allows monitoring, troubleshooting, and proactive network management using scripts and agents. The NAE does not help admins to manage multiple ArubaOS-CX switches together using familiar CLI commands.
That is the function of the ArubaOS-CX Fabric Composer (AFC), which is a software-defined orchestration tool that simplifies data center fabric management. Therefore, this does not correctly describe the ArubaOS-CX architecture.

Omit the device-specific settings from the configuration plan and include them in command scripts instead is not what you should do if you want to use NetEdit to manage ArubaOS-CX switches and deploy a standard config to the switches, but need the config to include a few device-specific settings such as hostname and IP address. This approach would require you to create separate command scripts for each switch, which can be tedious and error-prone. A better approach would be to use an auto config plan that uses scripts to customize the configuration for each switch based on variables such as serial number, MAC address, or user-defined parameters.