Yes, because if it didn’t support all scopes you would end up with services that would need their users to log in twice, once to get Kraken scopes, and again to get Helix scopes.
IMHO this is the misleading part: you’re saying that it supports both, but there are two table.
Every single API in the documentation has already specified the “Required scope”, so these tables are pretty useless if their only role is to exaplain their link with the different API (Helix/Kraken). I don’t know how people develop stuff, but I usually start from an API, and then I find what’s the scope required and I add it. I don’t think people start from a scope (most of the time the description is not so precise) and then they pick an API.
IMHO these tables should help to clarify what are the scopes supported by the authorization URL (all of them) and I don’t see any value in showing the supported API (and it generates confusion), because that information is already in the documentation. Another solution could be adding this information to the Authentication section.