I think the community here does not really like to keep questions with the correct answer "There is no broadly accepted name" alive on this site. The fact our experts don't know a common name for a "well-known concept" is often an indicator for the concept not being so "well-known" as the questioner expected, or it is just too general or vague to have a specific name.
IMHO it is fine when you ask such a question, but when you get the feedback that the impression of "there must be a name for it" was probably wrong, and the question gets closed, don't take it personally. Also, do not take the downvotes personally; the community people here often put them on a question to get it deleted more quickly, not because it was badly written. However, if it turns out some of the experts hastily closed your question, and some others think differently about the close and are willing to answer, this site has also a fair process to handle this, the "vote to reopen" process.
Finally, I think @RobertHarvey's comment is a bit overly harsh, since it implies you were talking about an anti-pattern or some code abuse, which you IMHO did not, but as I said, do not take this personally. See his reaction in a context where we get several of such questions each month asking for a "common name" when there is none.