You could look into making single purpose blocks. Then you can get listed in the block inserter upon search an site owners an install your block right from there. Some plugin developers made great inroads in active installs with this more friction less process. Once your block/plugin is installed you can provide links in the sidebar to more expansive plugins or premium versions.
The WordPress Block Editor offers two types of blocks: static and dynamic. The difference between these two types of blocks comes down to how they are rendered on the front-end.
In this podcast episode, Birgit Pauli-Haack and Mark Uraine discuss what’s new with Gutenberg in Gutenberg 9.3 review the upcoming Block Editor in WordPress 5.6.
The conclusion that sites installing the Classic Editor won't adopt to Gutenberg has a logical flaw. The Classic Editor is also used for sites, that are not "ready" for Gutenberg because it uses plugins that haven't gone through a full compatibility tests or where the site owner decided not to jump on the first version of WordPress 5.0 and waits until the kinks are out, say until 5.0.2 or 5.0.3. So there might be a lot more installs of the Classic Editor plugin coming, just because of this normal hesitance to jump on a new software feature out of the gate.