next/font moves font loading into the build, and shrinks the shift that swapping fonts causes.
Self-hosting. During next build, next/font/google fetches Google's CSS and font files, writes the files to /_next/static/media/ (served with Cache-Control: public, max-age=31536000, immutable) and puts the @font-face rules into the route's CSS. Loading the pages in Chrome 156 and Firefox 159 produced requests to the app's own origin only, none to fonts.googleapis.com or fonts.gstatic.com. That removes a third-party connection and the CSS-then-font request chain, and visitors' IP addresses never reach Google. next/font/local does the same for your own files.
Preloading. The files for the subsets you list get <link rel="preload" as="font" crossorigin>, on routes whose modules call the font function. The other subsets Google publishes are declared with unicode-range and fetched only if the text needs them: Inter got seven faces and one preload.
Less shift. Faces default to font-display: swap: text paints at once in a fallback and is redrawn when the font arrives. To make that redraw move little, Next adds a face named Inter Fallback that points at local(Arial) and rescales it with size-adjust, ascent-override, descent-override and line-gap-override values matched to Inter. The returned class sets font-family: Inter, Inter Fallback. At 18 px, a 60-character line measured 517.5 px in Inter, 515.5 px in Inter Fallback and 481.3 px in plain Arial. In Chrome, a 360 px-wide paragraph was 147 px tall in both Inter and its fallback.
The function returns className, style and, with variable, a class that declares a custom property for CSS or Tailwind to use. How CLS is scored belongs to Web performance.