bash direct path function calls work for SOME commands but not others.

Your system information

• Steam client version: latest
• SteamOS version: 3.8.16
• Opted into Steam client beta?: No
• Opted into SteamOS beta?: No
• Have you checked for updates in Settings > System?: Yes

Please describe your issue in as much detail as possible:

Describe what you expected should happen and what did happen.
launching a bash in gaming mode which used the command which by using direct path /usr/bin/which should result in the location of a command.

i used it in my script here https://github.com/EleriLove/More-Map-Variations-launch-script/blob/main/launch_nightreign.sh which is looking for the install location of ME3 to launch a game via steam,

this works in desktop mode like normal,

so does launching find using the same method even in gaming mode.

however for some reason /usr/bin/which me3 being stored as a bash variable and being called as such DOES NOT in fact run

Steps for reproducing this issue:

1. write a bash script using /usr/bin/which as a way to execute the which command
   2.run in desktop mode with it working as expected.
2. switch to gaming mode and run exact same script via steam
3. it will not work even though we call exact directory of command.

Start with the linked launch_nightreign.sh script and reproduce its /usr/bin/which invocation in SteamOS desktop and gaming modes. Compare how the command path is stored and invoked as a Bash variable, then confirm the behavior using the exact reproduction steps; done means the mode difference is explained and the reported invocation behaves consistently or its limitation is documented.