Can you tell us more about your high-level scenario and the problems you're trying to address? For example, how many different data collectors do you have? Do they use their own devices or share communal devices? Do they all have the same role? How many forms do you have? What is the connection between those forms? Do they all need to be available at the same time? Who determines what forms need to be filled when (e.g. the data collectors make the call based on training vs. a project manager communicates with data collectors)? How do you communicate with data collectors (e.g. Whatsapp group vs. in person)?
We've been working on getting better form segmentation at the server level since for a lot of scenarios that's what's needed. We've done this in ODK Central which is the replacement for ODK Aggregate. Everything in Central is organized by projects. Projects group together forms and app users. Typically app users represent a role like "health worker" or "lab technician". App users within a project can be given access to a specific subset of forms. This means that a specific data collector can see only the forms that they need access to from Get Blank Form.
Currently, if the form list changes over time, that requires manual management. In the next Collect release, there will be a setting to ensure that what the server provides as the form list for a specific app user is exactly what Collect shows in Fill Blank Form.