So - whether you display GUI or not is not terribly connected to what user context the installer runs in.
By default, we run things as LOCAL SYSTEM (which has the side-effect that if you were to SHOW GUI-stuff, it wouldn't appear to the user because of how Windows handles sessions now).
You *CAN* run things as "logged on user", (in which case they WOULD see GUI-things) but then have to (likely) contend with the "lack of local admin" permissions.
Option # 3 (in case "LOCAL SYSTEM" isn't good enough) is to run the package as "defined user" ... (domain, local, whatever).
Those are by and large your 3 basic ways to get things going. Whether or not you want GUI stuff displayed is not really directly affecting the user-context it's running in.
In terms of "whitelisting", sure that can be done (depends on your relevant software / component that's complaining) ... if we're talking UAC, then "installing as LOCAL SYSTEM" should not trigger UAC.
Do you have some more context / information here?