The old CrowdsourceReporter had category-specific geofencing built in. It could check what boundary a pin was in and then decide which request types were available based on that location. If someone was in the wrong service area for what they were trying to report, it would block the submission and show them who to contact instead.
The new Reporter Instant App added a boundary restriction option in the June 2025 AGOL update, but it only does a simple in/out check against one polygon layer. It can block submissions from outside the service area entirely, but it can't tie specific request categories to specific boundaries. There's no way to say "you're in a service area, just not the right one for this type of request."
So right now you can block people from submitting outside the overall service area, and you can show warnings with contact info for the wrong boundary using Arcade expressions in the form, but you can't hard-block category-specific submissions the way the old app did. That would require Esri to add that functionality in a future release.
