I could see maybe bundling those up into a simpler rule of just "make it easy to build on a windows machine". Outside of that, just my 2c, but I'd avoid adding rules that don't directly play into the theme or goal of the particular challenge/competition. If the goal is, for example, to examine certain gameplay mechanics, then it shouldn't matter what tools are used to get there. If the goal is maybe to teach how to make an ECS-like system, or to teach how rendering works, then yeah, you'd want to restrict the toolset in that case, since the rule then supports the end-goal.
This is keeping in mind again that if we're targeting beginners, limiting the workflow might again reduce the participants by those who aren't familiar or comfortable with certain tools or workflow yet. You could argue that it's part of the point, but it depends on what the stated goals of the particular challenge are.