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).
if (!preconnectsSet.has(key)) {
      preconnectsSet.add(key);
      const preconnectProps = {rel, crossOrigin, href};
      if (null === ownerDocument.querySelector(key)) {
        const instance = ownerDocument.createElement('link');
        setInitialProperties(instance, 'link', preconnectProps);
        markNodeAsHoistable(instance);
        (ownerDocument.head: any).appendChild(instance);
      }
    }
  }
}
function prefetchDNS(href: string) {
  if (!enableFloat) {
    return;
  }
  preconnectAs('dns-prefetch', href, null);
}
function preconnect(href: string, crossOrigin?: ?CrossOriginEnum) {
  if (!enableFloat) {
    return;
  }
  preconnectAs('preconnect', href, crossOrigin);
}
function preload(href: string, as: string, options?: ?PreloadImplOptions) {
  if (!enableFloat) {
    return;
  }
  const ownerDocument = getDocumentForImperativeFloatMethods();
  if (href && as && ownerDocument) {