BYTM needs some system to fetch dynamic data like DOM selectors from a place that's easily modifiable.
Since the host pages change their design and layout so much, this would make it a LOT easier to react to those changes and get the fixes out to BYTM's userbase without having to go through the entire deferred release cycle.

The easiest way to do it is to have a data.json asset (non-SRI, fetched from main branch).
This also has the neat side effect that a full static copy is included in the userscript bundle, so it'll always have valid keys to parse and values to fall back to that at least guarantee some level of usability.