We opted for the profile option using the linked profile editor for creation of the .xml file.
It worked like this:
Created a profile with a different name than our already-used webvpn.domain.org, went to Client VPN settings in dashboard and Enabled 'Profile Update' then clicked Choose File and navigated to the location of the saved .xml file, clicked open, then clicked to save in the Meraki dashboard.
Tested by loading a laptop pre-loaded with the Cisco Secure client from an off-network location, opening the client, entering the Meraki DDNS hostname and connecting. NOTE: Depending on the secure client settings, you might have to go into those settings and uncheck a Block Untrusted Connections box before completing these steps.
A pop up appeared saying the Certificate was untrusted. Clicking on "Connect Anyway" allowed the VPN to establish AND auto downloaded the profile for future connections.
Signed off of the VPN, closed Secure Client and reopened it and this time, the server name field was pre-populated with the VPN Name contained in the profile. Connecting to that VPN Name established the VPN without error.
Definitely the easiest way to accomplish what we needed and more cost effective!
Many thanks to the community and especially @PhilipDAth who didn't appear to get irritated by my many questions.