CloudWatch writing to expired logstreams?

We have a log group (with a 1-day expiry) set to receive events from Route53. Of course, these get split into multiple streams. We have an app that queries the last few hours of logs by requesting all the streams associated with the group and then filtering based on the last ingestion time before performing a regex on the remaining text.

For the most part, this works well but we have been known to miss messages. While looking into this, I found a recently written message (05/09/23 13:59:00) in a logstream that was marked as expired with a last ingestion date/time of 05/07/23 02:17:58.

By 15:37, as I am writing this, the last ingestion date on the expired logstream had finally updated. I understand these fields are eventually consistent, but I always thought of this as being a matter of seconds, not over an hour.

Given that this kind of delay isn't acceptable to our application, is there a better way to filter these messages or even receive them directly from Route53? Even if I took off the time-window in my call to DescribeLogStreamsRequest() I'd need to widen out further to get those marked as "expired" to cover this scenario, so I'm at a loss as to how this can be improved.