Is it possible to make programs interpret $ORIGIN in loaded shared libraries with the CAP_NET_RAW capability?

Question

I'm writing an application that has both Python and C++ libraries. The Python part needs to send and receive raw packets, so I'm giving the Python executable the CAP_NET_RAW capability.

I also load C++ shared libraries with Cython in the same program. I want to compile the shared libraries with relative paths for dependencies - i.e., use the $ORIGIN special variable.

However, because Python has the CAP_NET_RAW capability, Linux treats as a setuid program and ignores the $ORIGIN string inside the shared libraries' dependencies definitions, so they fail to load:

For security, the dynamic linker does not allow use of $ORIGIN substitution sequences for set-user and set-group ID programs. For such sequences that appear within strings specified by DT_RUNPATH dynamic array entries, the specific search path containing the $ORIGIN sequence is ignored (though other search paths in the same string are processed). $ORIGIN sequences within a DT_NEEDED entry or path passed as a parameter to dlopen() are treated as errors. The same restrictions may be applied to processes that have more than minimal privileges on systems with installed extended security mechanisms.

This security feature causes us a lot of pain. We have to compile shared libraries will full path dependencies and they are not portable between development machines.

Is there any way to disable this security feature in Linux so that $ORIGIN will be interpreted for programs with extra capabilities?