This is one of the frustrating things about Pagination in helix, as there are 2 issues at play here that can cause issues with paging through all results.
First, as you have to wait for a request to complete before you have a cursor to get the next page, you can’t do parallel requests so going through all >60k streams is going to take a while, and the longer it takes the more likely streams will go online/offline or change in viewership which leads to streams changing position in the results and leading to missing some streamers while counting some twice. The more pages you go through and time passes, the greater the degree of error.
Secondly, some Helix cursors just stop at the end of results, others such as Streams loop back around to the start again. There are several ways to detect this, either by checking the cursor (may not be reliable), checking for a large degree of duplicates per page, or going by the viewer count (if you were on pages with 0 viewer streams, and then start seeing a page with thousands for each stream in the page then you’ve looped back to the start).