While adding such as template shouldn’t be a big issue, the name with the “2” at the end could cause some confusion. Maybe someone has a good idea for another name.
I already changed a bit the proposal on the Talk:Wiki based on your feedback here since if worth the idea of have the template hardcoded to Wikidata endpoint, then at this point make sense to explicitly give visual hints on the generated template that it would run directly on Wikidata as opposed to Sophox, which really reserves to be default since it even allows federated query.
However, the Wikidata SPARQL does have not 1 by 1 equivalence on the query, so two templates make sense. Maybe in some place later I could document how to convert from the (proposed) Template:WikidataSPARQL to existing Template:SPARQL side by side.
PS: I not tested yet, but since SPARQL specification allow federate not just endpoints, but static files, in theory this would allow pre-process very heavy Wikidata queries in 5 to 100 steps and dump smaller RDF files and host like on GitHub pages, so Sophox (as long as some domain is allowed to federate on such static files) could be faster. So, while I’m interested on a direct to Wikidata SPARQL template (several queries I do have would be compatible inside and outside OSM), the Sophox already offers more than Wikidata public endpoint even for data on Wikidata which could be pre-processed ahead of the use. Fantastic!
Update: The code above already work on the OpenStreetMap wiki. The Template:SPARQL template (see Template talk:SPARQL - OpenStreetMap Wiki) was updated to allow customize endpoints so the idea of new custom template WikidataSPARQL is not necessary. Thanks!