vercel.com observed a bug where a stylesheet hoisted using a `precedence` was reordered after an update. This is not correct semantics (once a hoisted stylesheet is inserted it should remain in place until removed)

Investigating the React implementation I observed that if you insert a hoisted stylesheet during a synchronous render and later render a new reference to that stylesheet in a transition React incorrectly considers the stylesheet not loaded and tries to coordinate it's loading the the commit. This is erroneous as once a stylesheet is in the DOM it should never be re-inserted (moved).
let instance: null | Instance = hoistableRoot.querySelector(
        getStylesheetSelectorFromKey(key),
      );
      if (instance) {
        
        
        
        
        
        const maybeLoadingState: ?Promise<mixed> = (instance: any)._p;
        if (
          maybeLoadingState !== null &&
          typeof maybeLoadingState === 'object' &&
          
          typeof maybeLoadingState.then === 'function'
        ) {
          const loadingState = maybeLoadingState;
          state.count++;
          const ping = onUnsuspend.bind(state);
          loadingState.then(ping, ping);
        }
        resource.state.loading |= Inserted;
        resource.instance = instance;
        markNodeAsHoistable(instance);
        return;
      }
      const ownerDocument = getDocumentFromRoot(hoistableRoot);
      const stylesheetProps = stylesheetPropsFromRawProps(props);
      const preloadProps = preloadPropsMap.get(key);
      if (preloadProps) {