I would try, instead, disabling the menu commands in your template, either
manually or through code, once. Absent other weird Add-Ins, they will be
disabled when your template is loaded and not disabled when it is not
loaded.

Otherwise, your code would need to be very careful of the customization
context to avoid acting like a virus and permanently changing the interface.

If you would specify which menus/toolbars you are disabling someone here can
probably take a guess at what your code looks like. It will probably have
the term ".enabled = "false"" in it.

If you are hiding the standard or formatting toolbars your code would have
".visible = "false"" in it as well. You would want your exit code to reset
these to what they were when you started your code. These settings could be
saved in variables.

What follows is some code from one of my Add-Ins that changes toolbar
settings.
   Word.CommandBars("MyTools MenuBar Chas").Visible = False
   Word.CommandBars("MyTools MenuBar Chas").Enabled = False
   Word.CommandBars("Formatting Toolbar Holder Chas").Visible = False
   Word.CommandBars("Formatting Toolbar Holder Chas").Enabled = False
   With CommandBars("Macros")
       .Left = 521
       .Top = 23
       .Height = 28
       .Visible = True
       .Position = 1
   End With
   With CommandBars("CDEVTools Kenyon")
       .Left = 228
       .Top = 23
       .Height = 28
       .Visible = True
       .Position = 1
   End With

The first part disables a couple of command bars that are in the template
(they are only used for development, not general work). The sets of With
structures position two of the command bars where I want them.

Hope this helps.