Based on my reading of the Firefox code, the throttling profiles are hardcoded, and not configurable. Bug 1471539 (currently open) requests to make them configurable.
In the old times it was possible to edit browser/omni.jar (it's a zip file) and have the changes picked up after a restart. If that's still the case, you could make a separate install of Firefox and edit the hardcoded values (chrome\devtools\modules\devtools\client\shared\components\throttling\profiles.js
inside the omni.ja)
With appropriate experience, you could extract the code used to implement throttling and run it in the Browser console (in "chrome context"). (At first I suspected the network.http.throttle
preferences were responsible for this, but that's a completely separate thing related to throttling in background tabs.)
The most sure-fire option is to make your own build of Firefox, but that requires setting up and a non-trivial amount of system resources.
P.S. How large are your files? If the omni.jar trick doesn't work, it might be easier to select an existing profile and extrapolate.
PPS. You probably have your reasons not to use WebPack or another bundler, but I have to mention it.