DYLD_INSERT_LIBRARIES arm64 Ventura bug?

Prior to Ventura, you could compile arm64e dylibs, sign them, and inject them with DYLD_INSERT_LIBRARIES into some platform binaries (not all, mostly dev tools - debugserver, python, java, etc).

Post Ventura, we're getting an error of (mach-o file, but is an incompatible architecture (have 'arm64e', need '')). I would assume if the desire was to stop loading custom libraries into binaries they'd have the same limitation as other platforms binaries (which just ignore DYLD_INSERT_LIBRARIES, they don't crash), so not sure if it's intended, it's a bug or we need to add an extra step in order to load our dylib into such binary.