After investigating the issue, we have found that it's only present with the project attached. By removing the broken script reference from the UI Document and recreating the custom element(s), either through code or with the builder, using the existing or a new UXML, does not spawn the error mentioned.