If the directive is implemented, you won’t have to. Can can dictate it: If you target versions prior to 5.1, turn the wrapper off with the directive, and you know that it’s off. If you only target >= 5.1, turn the wrapper on with the directive, and you know that it’s on.
Completely off-topic, but I’d just like to mention it since I’m not sure if @rlkoshak ever became aware: Even though the “new YAML format” rules and rule templates PR is stuck, I did manage to get parsing of rule templates in the “old YAML format” (aka. the one in use on the marketplace) and in JSON format merged earlier. So, you can test rule templates locally today, by putting *.json or *.yaml files in conf/automation/templates. I just am not sure if you ever became aware of this. I haven’t documented it, since it’s all set to change anyway, but it’s there and it works. It’s using the exact same code for the parsing as the marketplace does, so you should be able to trust that what works there will work on the marketplace.