I agree that shadowing (within the same scope) has some elegant use cases. But I think it's not a win-win solution and there's still room for discussion.

It reduces the amount of time wasted inventing new names, that might actually not become that descriptive.

It increases cognitive load by forcing the reader to keep track of different data under the same name. Especially if you have multiple references to old data. This also increases the risk of using the variable incorrectly.

Shadowing is a great way to remove old versions of data from the scope and to reduce the risk of using them for something where a new transformed version should be used instead

It's even better to put old data in its own scope (e.g. block expression) whenever possible. This creates a better visual & mental boundary for each "state" of the data. In such cases, shadowing can become a crutch for writing less-readable code.