So no, GPL would have changed nothing. Companies would still have been able to ship it unmodified for free without contributing anything.
They could have kept their own code that uses FUSE secret, but even if they had had to release that code, that code is often useless to anyone else. It would not have helped or supported the author of the original code in any way whatsoever.
If they had linked against FUSE they’d need to provide code.
That way companies or other projects that won't touch *GPL for whatever reason have an option that allows them to use the code while helping the project.
Of course this could make the code incompatible with other open licence (or the licensing policies of some larger projects) so isn't a perfect solution. I'm not sure a perfect solution exists when the project maintainer(s) need income to be able to justify the time to continue their work and have not found some other form of sponsorship.
Alternatively, he totally could have gone and dual-licensed GPL and a permissive commercial license as a monetization strategy, like the author pointed out.
That can be messy for projects with many past maintainers where the licence options at the time of individual contributions did not explicitly allow this or arbitrary relicensing, but in this case (single current maintainer, other contributions made under a licence that allows him to do this) it needn't be.
Can you un-GPL your work for a single entity? Doesn't that mean that you yourself are violating the GPL? I'm legitimately asking, not being rhetorical.
But you can say, hey, I'm ALSO releasing this code under a separate commercial license that costs $X dollars to get.
You can't infringe on your own copyright!