No UUID affected to WSL instances

Is your feature request related to a problem?
Yes, this is related to a little problem indeed. I work on GLPI-Agent an inventory agent for GLPI to support WSL. We rely on some hardware informations to make accurate inventory assumption. On linux, these informations can be obtain from /sys/class/dmi/id or by running dmidecode. The most important one is probably UUID and

Describe the solution you'd like
It would be nice to be able to get UUID from registry on host side and from /sys/class/dmi/id/product_uuid on wsl side. A clear product_name would also be nice so we can be sure we are running under WSL. A serialnumber could also be nice.

Describe alternatives you've considered
Actually I implemented a WSL support for GLPI-Agent. The UUID on host is extracted from the GUID found in registry. In the case of WSL1 I'm able to write a file in the WSL FS so any running agent can read it back to find it's uuid. I've no solution actually for WSL2.

Additional context
Nothing to add here.

Start by examining how WSL exposes host-side registry data and the /sys/class/dmi/id/product_uuid path in WSL1 and WSL2. Determine whether UUID, product_name, and serialnumber can be exposed consistently, then validate the result from a Linux inventory agent in both WSL versions.