Can asset/resource modules be referenced in a dynamic entry function

[ModalityZ]

In a single build run, I want to walk a folder structure that contains json, css, images, audio, and mp4s so that when a leaf folder is reached, all the assets encountered along its folderpath are used to configure an entry point. To do this, I plan to use a dynamic entry function that returns an object where each key is a query-path and each value is a relative filepath to an index.js.
This works well for the index.js and json and css assets, but it doesn't yet handle non-inline assets. I believe I could do that via the js api. However, I can't figure out the following:

1. How does the js api relate to the way RsPack is invoked from the commandline to consume rspack.config.mjs? This would tell me how to inspect the Stats object when I build from the commandline.
2. How can the Stats object be accessed by the dynamic entry function?
3. In order to get files with content hashes in the filename for all my media files, do I add 'rules':'asset/resource' for all my media types to rspack.config.mjs as a sibling to the entry? That seems unlikely to be accessible to the entry function.

[ModalityZ]

I found a solution after a lot of experimentation, so I'll sketch it here in case it helps others:

1. The primary obstacle is how to make all the content-hashed filenames of the assets be used in .css and .html in place of their original filenames. This is usually achieved through plugin HtmlWebpackPlugin, but it doesn't handle MultiCompiler-formatted entry objects correctly.
2. Instead of introducing an array of invocations of that plugin as suggested in that link, which would be confusing as also explained in that link, call the RsPack JS API once on each key-value pair of the entry object. And in that call, use a single HtmlWebpackPlugin invocation.

Also, to answer my own numbered questions in the post above:

1. The configuration object passed into the RsPack JS API as the first parameter corresponds to the object that would be assigned to module.exports if one were using the commandline API. My new technique above cannot be done through the commandline API.
2. A dynamic entry function cannot access the Stats object, because Stats is the result of processing the entry value. To use the Stats value to configure the entry value, one would need to invoke the RsPack JS API first on a folder of resource files, then use the Stats of that to configure an entry or multiple entries for another run of the RsPack JS API.
3. To get content-hashed filenames for all one's resources, and update the references to those resources in .css files, something like this works (and the ordering of rules must place the css one first, as counterintuitive as that is):

module: {
      rules: [
          {
              test:   /\.css$/i
              ,use:   ["style-loader" ,"css-loader"]
          }
          ,{
              test:   /\.(jpe?g|png|gif|svg|woff2?|ttf)$/i
              ,type:  "asset/resource"
          }
      ]
  }