DeletedUser499
Have you considered using Molly with UnifiedPush set up and performing the same 'experiment'?
I really don't understand why you have such a hard time understanding that installing Molly makes it, by default, run a permanent websocket in the background that actively checks for notifications regardless of contacts being available.
The websocket implementation is not efficient, and I'm telling you that this is what is eating your battery. If you install Signal on a device without Google Services, it will use the same websocket implementation and also drain your battery. The only way to stop these messaging services from draining your battery is by using Google's Firebase Cloud Messaging notifications (FCM) which is what Signal uses by default when installed alongside Play Services, or use UnifiedPush on Molly to avoid Google's implementation.
There are dozens of individual threads on the forums accusing grapheneOS of reducing battery life massively. A lot of these issues have been solved by setting up Molly with UnifiedPush, or using Signal with Play Services to use FCM. I myself have fixed the exact same issue you are having by setting Molly up with UnifiedPush.
Or you could keep the conspiracy theory going, ignore all advice or explanations and bury your head into the ground I guess.
I cannot make it clearer to you what the issue is. I've told you the solution. Others have told you the solution. Please read.