The second thing is to log iMessage data on the server-side (since it has to be decrypted at some point). This would allow them to produce it, but would miss any apps installed on the phone used for alternative communication.
I don't like to see this so much as Apple refusing but there really isn't a way for Apple to enable easy full access without a backdoor, which is an unrealistic expectation.
iMessage is end-to-end encrypted, so that's also not an option. Apple would have to inject a key they controlled into a user's list of device keys. (Which they can do, and the UI doesn't notify users if it were to happen.)
Keychain, messages, and health data are all E2E encrypted and synced to iCloud.
By not doing iCloud backups, you're basically only giving up backups of app icon placement, home/lock screen background images, app data that isn't otherwise synced via iCloud or the app's dedicated sync service, and a handful of phone settings.
You can opt for the occasional iTunes backup to preserve those infrequently changing elements on the phone, and not have to compromise on recovery point for more important data like messages and security creds since all of that is synced in real time.
https://en.wikipedia.org/wiki/FBI%E2%80%93Apple_encryption_d...
Although it seems like it would be a RAM-only thing
If Apple does not give you the tools to decrypt messages on their phones, doesn't that make it "impossible" to automate, where automate is defined as any version of "decrypting the data on the phone"?