fyi: @jonaaa: open MemViewer~View, and you'll find 'Enumerate dlls' - [
[Link] ] - in there. Since i have the steam vs, i'd expect to find the steam_api in there...
But strangely enough, you'll also see Epic's eossdk dll loaded up here ?! I'm sure somebody has a logical explanation for this; pretty much out of my comfort zone to clarify this one. (=> so one/me could assume that the game will evt... etc

)
==> anyhow: the game_exe is built to load steam upon launch here; either initiated "directly" code-wise or via some setting (in some ini perhaps)? I'm (pretty) sure that the gamepass_exe is compiled in a different way/setting; thus producing different opcode (read: different AOBs)... (and almost certainly will not have steam/eos showing up in that list)
fyi2: you can compile (built if you will) an EXE using all sorts of parameters (incl optimization, compression, andwhatnot). Iow the very/exact same source code can produce many (different) game_exes (sort of speak)