Cannot view all processes without "run as admin"

[likely-misplace]

With Process Lasso's governor running as a SYSTEM Service, it appears to be applying rules to all processes on the system regardless of user (as intended).
 
I have a 9950X3D and the default rule is to assign a CPU Set of 16-31 (Frequency CCD), with an override of 2-15 for games (Cache CCD), and some overrides for specific applications to use 0-31.
This works rather well.
 
However, I log in to Windows with a Standard User account.
With Process Lasso starting automatically on login, I am only able to view processes running under my own user.

This can make setting up new rules rather awkward - as I often cannot see which process is causing high CPU usage etc.
I have to open up Microsoft's Process Explorer instead (running as the same logged-in user).
 
If I run Process Lasso "as admin" I am able to view and manage all processes.
But to do this, I have to manually close and re-open the app, entering the admin password.

Process Explorer does not appear to require running as admin to view things like system services (Windows Defender's "MsMpEng.exe" for example).
And Process Lasso surely has access, since it is running as a SYSTEM Service.
Would it be possible for this behavior to change?
I understand if it may not have permission to terminate processes running under other user accounts etc. But I'm mostly looking to be able to identify high-usage processes and create CPU Set/Affinity rules for them.

[Jeremy Collake]

Yes, conceptually it is possible, but is a large design change. I agree that it should be done and have created a ticket to track this. I'll reply again on any further news.

Thanks for the feedback!