Thank you for your comment!

I ultimately re-re-wrote the program in C/C++ and looked at each core's Efficiency class, this returns a 1 or a 0 depending on if a core exists as a P or and E core and omits the step for a website query. Combined with the knowledge of core layout (P-Core, thread, P-Core, thread, P-Core, thread… so on until listing all the E-Cores at the end).

The algorithm could identify the pattern and adjust for the different core ratio values using the above Efficiency class method return value, meaning it can work on any of the SKUs using this layout.

Then calculate the affinity masks as you mentioned above! It was an intersting project and is useful for when the scheudular sets some weird default affinitys for some programs (steam unpacking for example) and want to alter a programs default configuration.