Hello Dustin,
You’re correct! On Windows Server 2022 and newer, the old PowerShell method of adjusting per-host RDS collection weights through RDSessionHostCollectionLoadBalancingInstance[] is no longer a supported or exposed management path. That underlying .NET type/property chain was effectively removed from the usable RDS PowerShell surface, so there is currently no built-in, supported PowerShell command to set custom relative host weights in an RD Session Host collection the way older versions allowed. On current builds, Microsoft still supports changing collection-level load balancing behavior through the standard RDS cmdlets, but not per-host weighting through deprecated internals.
If you need to influence session placement now, the supported options are to drain or restrict individual hosts with Set-RDSessionHost -NewConnectionAllowed, split workloads into separate collections, or redesign broker behavior around collection boundaries instead of host weights. I would strongly avoid relying on old scripts that poke deprecated objects or WMI paths, because they are no longer reliable on Server 2022/2025 and can break after updates.
I hope you find something helpful with this asnwer. Please give it a thump up, or accept it if it's helpful to you.
Harry.