I think it might be the other way around. The glossary filter is processing the content regions created by the theme in a non-optimal way even when these content regions are empty and the theme is not even installed.

Why the content regions are becoming accessible to the glossary filter when the theme is not installed is another question.