Re option 3: relying on `DYLD_LIBRARY_PATH` or `DYLD_FRAMEWORK_PATH` isn't a great solution either because of SIP. It's can get impractical to use in many standard Makefile-based build systems, for example. (cf. https://github.com/qmk/qmk_cli/issues/60, https://github.com/Homebrew/discussions/discussions/1737) I imagine it can get quite vexing to set these variables but find them to not have the effect you expected them to.

One workaround for the example above would be to compile your own `make` program (or use one from a package manager) so that SIP doesn't sanitise your environment, but I imagine that's not an ideal solution either.