It also seems more reasonable to just leave it as a programming technique rather then give it artificial weight and call it some bloated unnecessary academic term "design pattern"
I'm guessing your talking about how iteration is implemented versus the action of iteration. Both are one in the same.
https://en.wikipedia.org/wiki/Induction_variable
Heck, originally, looping was performed by physically looping your instruction tape, and a break was pausing the machine to physically break the tape. Talk about a fragile design pattern!
The implementation matters. That's why people suggest using the iterator technique. It's not the best strategy for all cases, but it's generally better practice.
Take a look at the Wikipedia page for iterators, under the heading "contrasting with indexing". It's not explained super-well, but it covers a few topics.
Design patterns is a formalism behind common patterns in software, and part of that formalism is that they are named.
Obviously you don't need all that formalism every time you talk about patterns, the same way you don't talk about the laws of arithmetic every time you do math.
Design patterns is a unique phenomenon in programming. No other field is pretentious enough to refer to domain specific vocabulary as design patterns.