Yeah, I've just realised they've probably accidentally included a generic URL in the cache rules that they actually didn't intend to cache.
I originally thought they were trying to cache account data responses and so wondered why they wouldn't just use unique query parameters in that case. Definitely risky business though.
But what GP seems to be asking about is: “Would having your app always encode a user ID into the endpoint have helped?”.