Sorry if I wasn’t clear, the preferred method is using script tags, and not inlining the library code. This is so the reviewer can verify the integrity of each library file. They can’t do this if you inline several libraries into a single file.
Anyways, the rejection reasons are not relevant to the above, so it’s not the core problem.
As far as i know, twitch only tests the viewer experience of your extension. Anything concerning config or live config, they don’t test.
After skimming your video, it seems as if the extension needs streamer interaction to do anything, is that correct? If so - and because I believe twitch only tests the viewer experience - you may need to simulate the streamer interaction.
Here’s a quote from the extensions docs
Also, if your extension requires live data to operate, please simulate the necessary data to allow our reviewers to use the full breadth of features offered by your extension.
I’m not an authoritative source on how the review process works, i’m only speaking from experience.