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).
const instance = ownerDocument.createElement('link');
        setInitialProperties(instance, 'link', props);
        markNodeAsHoistable(instance);
        (ownerDocument.head: any).appendChild(instance);
      }
    }
  }
}
function preinitStyle(
  href: string,
  precedence: ?string,
  options?: ?PreinitStyleOptions,
) {
  if (!enableFloat) {
    return;
  }
  const ownerDocument = getDocumentForImperativeFloatMethods();
  if (href) {
    const styles = getResourcesFromRoot(ownerDocument).hoistableStyles;
    const key = getStyleKey(href);
    precedence = precedence || 'default';
    
    let resource = styles.get(key);
    if (resource) {
      
      
      return;
    }
    const state = {
      loading: NotLoaded,