(In Progress) Thoughts on Gen 1 Category Naming

Part 1: Instant Text
I have no problems with allowing instant text abuse in a glitchless run.  I have a very strict personal definition of what constitutes a glitch.  Glitches IMO involve causing the game to run undefined and/or arbitrary code.  The method to obtain instant text runs clearly defined code, and the fact that there is no defined code to reset your text speed is an oversight by the developer.  An example of how this definition works the other way would be the Brock Through Walls exploit.  This bug/exploit/etc is a true glitch under my definition, because there is no walk path defined for the character if you stand to the right of the NPC.  Another example that fits our current ruleset is poke doll in Lavender Tower.  The game defines the behavior of running from a wild encounter with a poke doll, and defines all the story-related conditions in such a way as to not require the game corner.
This definition of glitch cleanly integrates instant text into the "Any% Glitchless" basic category.

Part 2: Category Split Naming Conventions
Seeing that adding instant text makes sense, the next step is to figure out how to name the category that would disallow IT, Poke Doll, and Hard Resets for category parity with the Japanese speedrunning community.  It seems pretty well decided that the current category+IT will continue to be called Any% Glitchless, so the question is only about naming the new category.
Existing name possibilities:
Any% Glitchless + (classic, restricted, strict, No Major Exploits, JPN Ruleset, etc)

Classic:
Appending classic makes sense primarily from the perspective of the Japanese speedrunning community.  This ruleset will be classic for them.  Elements of it are classic to the Western community as well, but poke doll is only classic in the sense that it is the (Classic JPN Ruleset), which is why I might prefer including the regional distinction of the category in the name itself (but certainly would if classic is to be used)

JPN Ruleset
There is concern that including the term (JPN Ruleset) in the speedrun leaderboards itself would cause confusion.  I don't think that this is as large of a concern as the confusion of why the classic category contains elements that are not classic to Western community speedrunners.  There would be a category split for the various regional physical cartridges, and a secondary split for historical rulesets from various regions.  Even if this has to be explained, it is more logical than if the name just says classic and you have to explain "well poke doll isn't really classic to our community, etc."

Restricted:
I agree that this name and further a shorter name like "strict" could be slightly offensive to the Japanese Community's ruleset.  It might be worth directly addressing that though, because the name and similar ones like "limited" are easy to explain (it's a category with limitations on IT, Poke Doll, and Hard Resets) compared to classic or including a regional distinction in the category name.

Low Exploits/No Major Exploits:
I actually really like this naming strategy, but it has a pretty wide potential to be overly memed.  The previous suggestion (restricted) has a logical follow up "what are we restricting" to which the logical answer would be "exploits."  But actually using the word exploit in the name has been suggested to be too open to individual interpretation.  That is, chatters might be inclined to repeatedly ask "why is x thing an exploit, but not red bar or badge boosts???"  In my opinion, this is why Low Exploits is a sensible name.  It contains the same logical thought as (restricted) without a negative connotation against the Japanese ruleset, it's not saying that there are in any way -no- exploits, and it doesn't need to be verbose about the definition of exploit to get its point across.

TL;DR
Any% Glitchless (Classic JPN Ruleset) and Any% Glitchless (Low Exploits) would be sensical names in my understanding for both communities for the new category that will be created.