I'm going to highlight again that this is not the best practice, but as requested I'll share some insights on a possible solution for problems related with this pattern.
If you have an ordered list, and it keeps the same order after the process, you can add an input to the screen to inform the aggregate of the record row index you want to target. To avoid performance issues you need to pre-index your records and filter it by a range, for example from Record.Index < TargetIndex+10 && Record.Index > TargetIndex-10. That will bring you issues with the scroll behavior and you'll need extra logic to take care of that feature. Not to talk about searches... so, again, i advise everyone not to follow this kind of cheap tricks.
This kind of advanced solutions are possible, but they need to be analyzed for each individual use case, there is not a generic list solution - At least apart from what the platform already does for us, which is already pretty good and most of the times enough!
Regards