None of the papers linked above or linked in the GitHub repo mention “loop resistance.”

Not completely different; they're both sequential access patterns and equivalent whenever the loop size exceeds cache size.

Not equivalent completely. Scan is a one-time access, so it never hits in scanning. Loop is multi-time accesses, so it can get many hits in looping if it has loop resistance. No hits on scan resistance in looping. Over.

I am disgusted by people who are repulsed by even the correction of a complete error. They must have bad grades in college. From now on, we have no choice but to leave it alone even if a false rumor is spread.