That’s what I thought, thanks: it’s hierarchical, so it can affect a child directory of the WordPress installation, but not a sibling. It looks as though the problem was unrelated to BPS, and having it show up at the same time BPS was installed was a misleading coincidence.
WordPress is installed in mydomain.com/blog; Vbulletin is installed in mydomain.com/forums