AWS Support doesn't know your workload. If you, who know your workload, can't figure out what's wrong, how can AWS Support figure it out in 15 minutes?
> "that got an answer of 'looking into it' in 19 minutes, then ~1:45 an answer of 'oh, yeah, I checked and this and this DB you talked about didn't reboot', which was true, the person that made the ticket pointed out the wrong instance."
Which wasn't AWS Support's fault. They looked into the resource on the ticket. Again, AWS Support doesn't know your workload and isn't going to go on a fishing expedition to guess which DB might be the issue.
> "3 hours after I point the correct DB we get told, yes, you are right, it rebooted. And then on the 1st of April I ask for a timeline of how the writer/reader nodes changed during the reboot, I get an answer on the 20th, even though we pushed in the ticket and through our TAM for an answer."
Timelines and RCAs have to go through the service team. Up to, and including, the service GM at times. It can be frustrating to wait for an RCA, but sometimes the things just take time.
> "All in all, for the hundreds of thousands of dollars we're spending a month on support, I have a feeling that when we need it, we're kind of alone."
I'd encourage you to open a chat or phone for a business critical issue. That way Support doesn't spend an hour and a half trying to troubleshoot the wrong resource. Those errors can quickly be found and remediated on a call.