Need a new EXEC CICS INQUIRE browse command, or a modification to EXEC CICS INQUIRE UOWENQ browse

Need a new EXEC CICS INQUIRE browse command, or a modification to EXEC CICS INQUIRE UOWENQ browse, to allow a program to quickly find out the owner of and waiters for any resource that can be enqueued upon with EXEC CICS ENQ.
Currently, an EXEC CICS INQUIRE UOWENQ browse can be used for this purpose however when there are lots of enqueued-upon resources, performance is intolerable.
.
Consider the following situation: Task1 has updated thousands of records on a recoverable non-RLS VSAM file and thus owns that many enqueues in the FCDSRECD pool. Task1 now suspends for a long time. Task2 has done an EXEC CICS ENQ RESOURCE('ABC1') LENGTH(4). Task2 wants to know what other tasks,if any, are waiting on that ABC1 ENQ.
.
Task2 can do a EXEC CICS INQUIRE UOWENQ RESOURCE('ABC1') RESLEN(4) START and then proceed with the browse. This will return information about all enqueues from all UOWs that own or are waiting on resources that begin with ABC1. (Note that this could include UOWs that own a record lock on a non-RLS VSAM file whose dataset name begins with ABC1, in which case TYPE(DATASET) is returned. Or as another example it could include UOWs that have done a WRITEQ to a logically recoverable TDQUEUE named ABC1.) The problem with this is that performance is intolerable. Even though the browse is filtered by Resource, internally, every UOWs chain of enqueues is looked at. To process the UOW that did the thousands of VSAM file record updates takes up potentially several seconds of wall-clock time. And if Task1's UOW is prior to Task2's UOW, then those several seconds of wall-clock time happen before the 1st Getnext has returned to Task2.
.
Task2 could also specify its own UOW as input on the INQUIRE UOWENQ START. That would limit the browse to just those enqueues owned or waited on by Task2. That way would solve the performance problem caused by all of Task1's enqueues, but it would not return any other UOWs that are waiting on the ABC1 enqueue. So that doesn't work for that reason.
.
There needs to be a way for Task2 to request to browse through the owners and waiters for a particular EXEC CICS ENQ resource without incurring the overhead of internally having to browse through all enqueues of all UOWs.