DLL Hell is something entirely different. The term comes from a time where Windows installers actually installed an applications required libraries in the "system location". So if application Foo is installed, and uses library Bar version N, but then you install application Baz, and it uses library B version N+M, suddenly Foo no longer works.
Modern "application bundle" approaches don't do this, because they keep any required shared (i.e. non-statically linked) libraries private to the application (bundle). This is what MacOS has done since its inception, and it has never suffered from DLL Hell.
The one notable downside is when there are vulnerabilities discovered in code ... the "traditional" Linux approach means that a system update can fix all applications in one step, whereas the bundle approach breaks this.