This isn't true. OEMs have been forbidden from publishing "incompatible forks" of Android. Incompatible being: Not having Google's apps, which are required to pass the CTS. This is one of the reasons the EU levied it's record-breaking fine against Google for anticompetitive behavior. (It's likely EU MADA contracts have been revised to remove this requirement, but I wouldn't be surprised if they still enforce it elsewhere.)
F-Droid has a very tiny portion of apps, similar to as many as Purism itself will likely handle using it's own Linux-based system with an app store. Most common apps people expect require Google services on Android, as Google has let the open APIs languish and pushed everyone to use, for instance, Google Location Services, which is proprietary. Apps like Uber or Lyft, for instance, require Google. Hilariously, a lot of Microsoft's apps, such as Skype, require Google, despite being a competitor.
As long as Android's app library is primarily built on Google proprietary code, there's no point in bothering to maintain compatibility with a slow and sluggish, locked down Java-based OS.