JSF summarized my point very well.Come on mate, there is a difference between filtering something in an ad-hoc search functionality (extremely simple to implement) and determining which fields you can use to assign cases to individual IRCC officers. The 2nd isn't a simple search-results functionality. The configuration for it is certainly not accessible to most system users, as there is a 0% chance that IRCC officers can select their own cases. So it is an admin-level functionality. There is a real chance their system cannot assign cases by CoR - and there may well be ethical/non-discrimination reasons for doing so.
Along those lines, the document you attached clearly indicates that officers are leveraging the CoR in the application details - not in a table format. So they are using this to interact with cases they have already been assigned.
I'm talking about the functionality on admin level itself. Admin level, meaning the person who assigns cases to the officers or agents. Think of it as like an table view, where the person can select multiple applications depending upon the criteria with not just CoR but others too like medical expiry date, COPR expiry date, etc and they can implement some functionality on those applications like assign Officers to certain type of applications, extend those expiry date or move them to a different VO.
I strongly believe they have such a system, not exactly like I said but in some form because else it would be a huge system design failure. There are n number of scenarios for which they need it. We know for the fact that VOs are changed in the middle of processing at times, maybe to reduce overloading. We know most of the cases with applicants in US and Canada are assigned to Montreal. Let's take some more hypothetical examples, lets say there is a Kabul VO which also processes application from nearby countries like iraq, pakistan too and they have to suddenly shut down their office overnight, IRCC needs to move those applications to other places too. This is how they are right now processing afghan applications on priority. How else they will know if an applicant is from aghanistan or not from thousands of refugee applications from around the world. Even there would be plenty of FSW applications from afghanistan who may have sensed the crisis coming and applied to Canada before anything unfolded. IRCC has to prioritize those applications too regardless of the fact that they didn't apply under refugee. Another case scenario would be, lets say xyz college was fake or someone forfeited offer letters of that college and got n number of students approved or in process of approval for their visa, now IRCC came to know after sometime and needs to reevaluate those particular applications. Same applies to lets say xyz company was fake and number of pr applicants used it to score points. It would be hard for IRCC to find each of those applications without filtration or some sort of system, and they would reassign all those applications to certain VO or officer who is knowledgeable with the situation and can take proper action rather than giving it to random officers and then dealing with court appeals for unfair treatments. Even it applies to lets say abc employee who is a super-admin got corrupt or high one night and abused the system to (dis)advantage certain applications. My point is, there are n number of scenarios and risk mitigation purposes for which IRCC needs a system where they can filter and process certain applications, whether it is by CoR or anything else.
Again, we all can just predict and challenge what might be the system on their end. We might never know, for sure.
Maybe, you are absolutely right and they can never be able to distinguish Inland and Outland applicants. But I like to think it optimistically that they have a system which they will use it right now or in near future for us.