p5 loadFont() and its dilemma with opentype.js

Topic

As @amehowc mentioned in his p5.varaibleFont library
There are two primary methods for loading and using fonts in p5.js. One involves using loadFont(), and the other is by defining a font either through CSS with a @font-face tag or importing it via an API like the Google Fonts API. Both methods have the same end result when using text() in the 2D context. However, differences emerge when you delve into font data functions like font.textToPoints() or font.getBounds(), or when using the WEBGL context.

Basically it could be drawn into a table like this:

O = supported feature, X = unsupported feature

The two ways of loading fonts create different supports in p5 for these typographic related functions.

Supports for native Canvas API

• If you rely on using opentype.js to parse through the font, you get all the vertices of the font, and can draw them even in WEBGL mode.
• However, you will lose important supports like controlling the texts with native Canvas API (because Canvas doesn't recognize this as text anymore, but vertices with text shapes). This is really major because p5 inherently is built on top of HTML Canvas, which is a relatively new element in web technologies. Many things that have long been requested by the community are slowly being added in, such as letter-spacing or fontStretch. We might be reinventing the wheels here if we decide to not have it support native Canvas APIs.

The loadingFont function

Basically if you import font using the loadFont() function, it will still create a CSS @font-face for you in the code as shown here in loading_displaying.js:

https://github.com/processing/p5.js/blob/36437b3d68bc651b8695a401159eef36aeec5881/src/typography/loading_displaying.js#L125-L133

However, it will not be referencing it, so I'm really unsure if this part of the code is even working.

Start with src/typography/loading_displaying.js at the linked lines and trace how loadFont() creates and uses its CSS @font-face entry. Compare the observed behavior with the issue's support table across 2D, WEBGL, Canvas, variable fonts, and p5 font functions; done requires an agreed, explicit direction for these loading paths.