iPhone 13 Understanding uncommon daemon exercise (UNKNOWN PID) and excessive background community utilization in iOS 18.6.2 logs

I have been reviewing some diagnostics logs (.ips, .synced, .session) on my iPhone 13 (iOS 18.6.2) as a result of noticeable efficiency points, and I discovered a recurring sample within the system daemons that I am struggling to interpret.
Listed here are the primary technical anomalies I am seeing throughout an 8-day interval:

1. Persistent UNKNOWN Course of (PID 31)
   Throughout a number of logs, a course of recognized solely as UNKNOWN [31] repeatedly brought on CPU maxing occasions by way of the duetexpertd daemon. In a single extreme occasion, there was an enormous disk write occasion (1 GB written in 100 minutes, at 14x the system restrict) attributed fully to this UNKNOWN course of.
2. Excessive Background Information Switch (nsurlsessiond)
   The nsurlsessiond daemon generated a write abuse report displaying a switch of 1073 MB of knowledge within the background inside a 22.5-hour window. The system was constantly related to a steady Wi-Fi community your complete time, with no drops or switches to mobile information. The ‘On Behalf Of’ discipline factors to unidentified purchasers, together with UNKNOWN [-1] (which appears invalid), UNKNOWN [33], and UNKNOWN [3031].
3. Digital camera Daemon Exercise with Display Off
   A Jetsam report taken whereas the display was utterly off (brightness 0.0) and idle (idleDelta=0) reveals the cameracaptured daemon energetic for 149 seconds. This creates a discrepancy, because the official Digital camera app solely registers 49s foreground / 3s background.
4. iCloud Identification Failure
   There’s a vital failure logged for Apple ID verification relating to iCloud Safe Backup:
   • Error: CloudServicesErrorDomain code 212
   • inCircle: 0 (system exterior the belief circle of iCloud Keychain)
   • HomeKit additionally generated missingKeyTypes: 126 errors in CoreDataCloudKitExportEvent.
   My questions:
   Is it regular for iOS to assign low PIDs (like 31) to processes that present up as UNKNOWN within the logs and trigger this degree of useful resource consumption? Might this mix of heavy background community transfers, daemon CPU maxing, and iCloud sync failures be a identified bug or reminiscence leak in iOS 18.6.2?
   Any insights into studying these particular diagnostic patterns can be enormously appreciated. Thanks!