You can try to do this with rpath of $ORIGIN. But then you'll probably still run into libc issues -.-
Not hard to see why a lot of games focus on Windows and let wine/proton handle Linux.
Linux (g)libc is sort of equivalent to the Win32 API on Windows so you are not expected to ship your own version just like you don't ship your own ntdll, user32, etc. Since glibc has good backwards compatibility the onlye libc issue you will run into is having to compile against the oldest version you want to support.
The idea of doing that for the DLL search in Windows could have been inspired by C.
GNU/Linux doesn't have DLL hell only to the extent that there is an entire binary distro with maintainers beavering to keep all of the dependencies straight so that every program that needs a certain shared library is maintained to need the same version of it as any other program.
You will experience shared library hell as soon as you have your own binary application that is not in the upstream distro, and it happens to depend on one of the lesser libraries that do not do symbol versioning like openssl, libbz2 and whatnot.
I've dealt with this plenty in more than one Linux embedded dayjob. In one case, I hacked an elaborate library searching system around dlopen() into such a program.
It's the original fix!
However there is also the WinSxS alternative, adding a manifest file to the executable.
does precisely that. @executable_path is evaluated at runtime.
Since nix stores everything at /nix/store, I didn't want to mess with relative paths...
But yeah, macOS apps can ship their own version of libraries thanks to this flexibility.