Does babel-polyfills have any strategy to prevent creating cycles?

From https://github.com/babel/babel/issues/8754:

> Compilation of `node_modules` is becoming more common as more packages are publish as ES6.
>
> This is causing problems in two ways:
>
> * `transform-runtime` can potentially insert references to `core-js` into `core-js` itself
> * `transform-runtime` can potentially insert references to `@babel/runtime-corejs2` into `core-js` itself
> * `transform-runtime` can potentially insert references to `@babel/runtime-corejs2` into _itself_, causing dependency cycles
> * And similar with `useBuiltins: 'usage'` transforming `core-js`.
> [...]

I think the same question needs to be discussed here.

Start by reading the linked Babel issue 8754 and the examples in this issue concerning transform-runtime, core-js, @babel/runtime-corejs2, and useBuiltins: 'usage'. Determine whether babel-polyfills has an established cycle-prevention strategy and document or agree on the intended approach; the issue is complete when that strategy and its scope are clear.

Written by the indexing model from the issue text.