Is it a good idea to wrap the graphql queries through meteor methods? Why I would like to check such option is to prevent exposure of the queries to the client via isSimulation check and dynamic imports.
What exactly are you trying to secure? The queries are - like the templates, a public thing. Everything on the client should be considered public and insecure. If you don’t want to expose any query because you dont want to expose the fields, then don’t use graphql for those calls. So I would not recommend this approach.
You can do it however, because a graphql query or schema is just a string. You can fetch it using a method and then use it directly on your query component.