May I ask for some motivational use-case? =)
Of course

The use case is when the Amiga system's isn't really online, but only is on a IPv4 peer-to-peer link to a modern system, that is on an IPv6-only LAN, using NAT64/DNS64 to access the legacy IPv4-only services - such as the UHC search sites - perhaps not a common scenario today, but one that may become more and more common in time

Has the 3.2 team been notified about the great RequestString suggestion and the Multiview search limitations?
Yes, silence regarding RequestString, and a plain "no" on the Multiview search, it simply isn't available for Amiga guide datatype, and it isn't programmable.
One thing I also can recommend is to set the UHCREADER ENV variable to say Multiview or MuchMore.
I looked into my ENVARC: the other day, so much UHC#?

Perhaps an idea to put them in a folder? ${UHC/VIEWER} for example..
Damn, I now found another bug in OS 3.1.4 (and earlier)...
Setenv UHC/VIEWER Multiview
It creates ENV:UHC folder and the ENV:UHC/VIEWER file with correct content.
However
SetEnv SAVE UHC/VIEWER Multivew
does not create ENVARC:UHC folder and ENVARC:UHC/VIEWER file...