GUID , display.card, camera etc interface mac address can share OEM.Key at multiple-network(v4, v6 )?

Question

GUID , DisplayCard, camera etc. interface(s) , their mac address(es) can share 1 OEM.Key at the
multiple-network (net.v4, net.v6 when ISP yet IPv6 fully , or in case OEM firmware later off updated ) ?

Refer: https://superuser.com/questions/1108151/windows-license-stored-in-uefi-bios
As to whether you can access the table to alter or edit the Product key? I just found out about the product key in the eufi, we'll have to wait and see. I will follow up. The key is injected at the mfg not in Redmond so I'm thinking the mfg gets a tool. I will ask for one. But the oem should be based on GUID. if you add, remove, or replace any hardware device that is in the GUID, the computer will get a new GUId. This probably only applies to people who want to escape their OEM product key. I think the sound card, graphics card and network card and processor make up the guid. Just change one of them for a new number and you should be able to escape out of the OEM label.

ACCORDING TO resources : QnA-noreply@microsoft.com [upd May 17 2022]

one of examples would get this question to be possible share hardware from SDK, Visual Studio sort of such by ...
Refer :
https://learn.microsoft.com/en-us/answers/questions/760023/how-do-i-configure-my-multithreaded-net-6-applicat.html

"migrate a project from .NET Framework 4.7.2 to .NET 6, but the performance of my program has dropped significantly. Parts of the program exploit parallelism for bulk operations on a server with 96 Cores and 192 Logical processors split across 4 CPU groups"

/
visual stadio .NET 6 or SDK quite "pretty on such among cores, CPU all related hardware staffs manipulatable "
/
In .NET Framework 4.7.2 we used the following app.config-file which successfully made the program run across all 192 Logical processors, achieving ~98% CPU utilization:
/

>>> version(s) recorded all of timestamp's app type and , the app status at somewhere ?

According to Microsoft's own documentation app.config is not used to configure .NET Core projects, replaced by [appname].runtimeconfig.json. To accommodate this change i have added a runtimeconfig.template.json to my project:
https://learn.microsoft.com/en-us/dotnet/core/runtime-config/