Hello Johann,
Thank you for posting question on Microsoft Windows Forum!
Well! The actual IP/DNS values are kept with the TCP/IP adapter configuration in the registry/NetTCPIP store. Not inside the WLAN profile XML that netsh wlan manages. The Settings UI for Wi-Fi profiles is just a modern (UWP) front-end that tells Windows which TCP/IP settings to apply to the adapter. Since Windows requires elevated privileges to change adapter TCP/IP values, there is no supported non-elevated netsh wlan equivalent to set IP assignment to Manual for a profile.
Per-interface IP/DNS values, Windows stores, are persisted under the TCP/IP parameters in the registry HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\Interfaces<Interface-GUID>. These keys reflect the adapter’s IPv4/IPv6 addresses, gateways, DNS entries, DHCP flags. On the other hand, the Wi-Fi profile XMLs that netsh wlan can add/export do not include TCP/IP static IP or DNS settings. Those are separate. The Settings app uses the newer networking APIs and UWP context to flip the adapter’s TCP/IP configuration; the classic CLI/API (netsh / NetTCPIP) touches the same HKLM keys and therefore requires elevated/network-config privileges. As a result, the IP/DNS are applied to the adapter, not stored inside the wlan profile XML.
Hope the above information is helpful! If it is. Free feel to hit "Accepted" for benefitting others in community having the same issue too.