You could store the file position OR closest offset value every 5% in the dictstat2 file for each wordlist as mentioned in first post. Maybe only do this for wordlists over 1GB? Hashcat actually displays the % progress from the --skip value anyway so, all you do is round-down to nearest 5% and move to that byte value if possible:
Live Example: Progress.......: 12814444170/14481290158 (88.49%)
88.49% = 85% nearest so, only have to read the remaining 3.49% and we are off cracking again.
(14481290158 * 0.85) = floor(12309096634.3) = 12309096634 offset (now we have file position @ 85% when building dictstat2). I don't fully understand how dictstat2 stores the wordlist data so might not be possible.
Live Example: Progress.......: 12814444170/14481290158 (88.49%)
88.49% = 85% nearest so, only have to read the remaining 3.49% and we are off cracking again.
(14481290158 * 0.85) = floor(12309096634.3) = 12309096634 offset (now we have file position @ 85% when building dictstat2). I don't fully understand how dictstat2 stores the wordlist data so might not be possible.