Hi @ali moghtaderi ,
Thank you for listing the constraints, what you have already tried, and the point that you only need the registry reads that are actually required rather than broad access. That made it much easier to check each part of the question against the documentation.
Your reading of RegOverridePredefKey matches the documentation, and I could not find any documented mechanism that goes beyond it. Within the constraints you listed, I found no supported way to give the unmodified executable and its native child a private read-only registry view before their first registry access, so there are no documented APIs, activation context, inheritance rules or version requirements to apply here. While this is not the outcome you were hoping for, it does give your design review a clear basis: any approach that tries to do this would depend on behavior Windows does not document.
The RegOverridePredefKey function reference states that the remapping affects only the calling process and that the function is intended for software installation programs. Nothing on that page extends the mapping to another process or to a child.
On inheritance for the native child, AppContainer for legacy apps states that an AppContainer process and its child processes can access only the resources specifically granted to them, and that a child created with CreateProcess typically inherits the parent's token. That is the documented behavior that applies to the PowerShell child in your scenario.
As for necessary versus optional reads, Windows PowerShell 5.1 does not publish the registry keys it reads at startup, so Microsoft documentation does not distinguish the two.
What I can confirm from the forum is limited to the public documentation above. If you need Microsoft to formally confirm supportability for this design, Windows Developer Support can take it to the product team. Including the Windows build, how the LPAC token is created, the exact key in the error and the constraints you listed here should help them answer without another round of questions.
I hope the documentation I found helps you move your design review forward. If this helps clarify where the documentation stands on your scenario, I'd appreciate it if you could take a moment to follow the steps in this guidance, so others with a similar scenario can find this information more easily.
Thank you.