The problem with going Enterprise route is that you can't just get Windows 11 Enterprise client and not join it to a domain because quite a number of group policies that control all the advertising junk, recommendations, and data siphoning won't work without domain. You are looking at the cost of Enterprise license + Windows Server Standard License at the minimum.
Been using enterprise clients without a domain basically since they were invented and never had any issue disabling the junk settings. Got the home-lab running on a Windows 2022 server and a mix of Windows 10 and 11 clients (most is really Linux) very much in a "Windows 3.11 for workgroups" setup just fine, with file and printer shares working and zero AD anywhere. Mostly, because I don't believe in creating a single point of failure when I don't need one.
Except that doing those privacy settings it is a nuisance, you have to do it on every machine and to a certain degree for every user. It's one of the things I like about Windows 2022 server: It comes without most of the junk by default! And still works very much like a desktop, except for some vendors like AMD cheaping out on driver signatures. Otherwise I'd run server 2022 on all machines just for not having the junk! (MAK keys help)
There is still the local policy editor which you can use for things like deactivating "com-plot", perhaps also recall.
And I'm sometimes using NTlite to set these policies on the image to cut down on these repetitive settings, eleminate modules I don't want (even Edge!) and I deactivite the user experience daemon, which seems to be the main conduit for phoning home.
In short, in my experience there is nothing an Enteprise client variant will not be able to do that the lesser variants can.
While I'm waiting for the LTSC image to arrive, I've just done a IoT 23H2 installation on a Skylake laptop, which normally won't accept such an older machine, even if it is actually functionally identical to Kaby Lake variants that are "acceptable"...
Rufus eliminated the stupid obstacles and IoT meant that I didn't even have to use an activation key, which is rather useful since this is on a SATA-SSD in a caddy that's moved between systems quite normally. Normal enterprise variants with a MAK move easily enough but may want an extra reboot after moving between hosts.
Only getting it on a fast USB stick for that extra mobility still requires a disk management tool. Microsoft still doesn't want to you install on USB by default...
I got MSDN from my employer so I don't have to organize my lab around M$ licensing obstacles. If it wasn't for that, I'd have long gone Linux exclusive, just because of the overhead!
And here is a bit of heresy: Windows images move and upgrade far more easily between hosts than any normal Linux these days. I got Windows 11 images that started as Windows 7 and have moved and multiplied and upgraded among dozens of physical and virtual machines. The Windows 7 style user icons (e.g. guitar) prove it!