it is possible, yes, it would require some modification to the script that indexes the packages.
why curl people need direct access to OpenWrt package binaries? Can they just tell people to opkg install curl on OpenWrt?
and if they are scraping HTML why not scraping the download server landing page https://downloads.openwrt.org/ to find whatever is latest version and the list of targets, then you can assemble the download link for the package (again in the download server that you can also reach by just clicking around if you are not a scraper bot limited to text)
I mean, I'm already scraping from that site and from manifest files anyway, it makes little sense to scrape to create a html that is scraped again by someone else that could just scrape the same source instead.
Also people that want to download packages manually should go there.
EDIT: My intent here is not "brushing off" anyone, it's just that the OpenWrt wiki is not meant for machine interaction, if you need interfaces for machine interaction there are better ways (that I also use to create the package lists) so if that is required just ask for that directly and we can explain how or if it's missing we can create it. For example in the past I sent a PR to the OpenWrt build system to keep a "verbose" version of the package manifest text file in the download server that is used only for my script to read/parse information. for example this https://downloads.openwrt.org/releases/21.02.1/targets/x86/64/packages/Packages.manifest
Also I think aparcar has a more modern system based on json and python or something, which is probably better suited for more modern tools. https://github.com/aparcar/openwrt-json