This is difficult to answer. At a glance, you're asking the kind of question that would make an agile practitioner wince. Your reasoning also reads as if you're prioritizing your personal ("the few") comfort higher than the team's ("the many") success.
Setting that aside, some questions.
When you say "they have decided", who is they? Management? The development team? What's the role of these requirements in your project? When are they written relative to the rest of the project cycle, who writes and maintains them, and who is their audience? Where does the audience tend to work from?
If the team made this decision, shutting it down unilaterally means you
are not agile, please gather your things. If management made this
decision, start by talking to your team.
If you're defining full requirements up front (this is the part that tends to cause wincing), then the most critical audience is the development team, and they hopefully start at JIRA or some other task-oriented tool (friends don't let friends use Confluence as a task manager).
In this case, the document layout matters a lot less than keeping the contents linked to the JIRA tasks for implementation. If your team is using stories, each story in JIRA should be a hub and a home page for all of the information your team needs to build it from start to finish. If your team knows they can start from the story and find a clear path to the Confluence page, it doesn't really matter where that page is.
If you're interested in some documentation layout ideas, and you're using things like stories and epics, consider looking into user story mapping for a two-dimensional way of looking at the bigger picture and forming a documentation scheme from that. It plays very nicely with Initiative > Epic > Story hierarchy along with free-form Theme tagging (in case you ever buy into Atlassian's Portfolio product). This sort of hierarchy + tags scheme maps to a Confluence page tree + page labels approach quite painlessly.
It also aligns with JIRA and Confluence's native prescription. Confluence's out-of-the-box requirement templates behave like Epic pages with Story tables, and JIRA Agile's Epic management has Confluence page linking plastered all over it. Atlassian wants you to make Epics the smallest unit of 'page' in Confluence, so go for it.
Just try to remember that requirements up front are themselves very much a product, and like a product they have their own requirements and customers who have a say. Make sure whoever will actually be using your requirements has an active role in deciding how they'll be delivered.