Step 1. Get around the Info.plist check for Aperture by changing its bundle identifier.

To make things work, we have to start somewhere. A Google search shows Exceptions.plist in CoreTypes.bundle is responsible for what is and what is not allowed to launch in macOS.

/System/Library/CoreServices/CoreTypes.bundle/Contents/Resources/Exceptions.plist, opened in BBEdit

Found it! Instead of editing this file to flip the <true/> flag (which would require disabling System Integrity Protection and mounting the system volume as read-write), we can use a safer approach that doesn’t require disabling System Integrity Protection:

Because we know macOS blocks Aperture from launching based on checking for its bundle identifier, the safer approach is to directly edit Aperture’s Info.plist and changing its bundle identifier into something else.

Go to the Applications folder in Finder. Right-click on Aperture.app, and choose “Show Package Contents”. Drill down into the “Contents” folder, and open Info.plist in BBEdit.

Appending a digit ‘3’ at the end of ‘com.apple.Aperture’ and saving the file should suffice.