The fact that the Scroll API is not recommended for deep pagination in ES 8 is well-documented. I'm currently updating some legacy code which uses it to page through a result set much larger than 10k hits, and from what I've read so far, it seems like search_after + PIT mainly exists to support realtime operations/lower request overhead.
My code is a long running job which I have the luxury of shutting down traffic to the cluster for whenever it needs to run. With that in mind, is there any danger in continuing to use scroll this way until I have time to go back and replace with search_after + PIT, or are there other issues with this that I am not considering?