(context: I help make Obsidian)
Canvas can be disabled in Core Plugins, like most other features.
In general I mostly see the opposite criticism: that Obsidian out of the box is too barebones and that it requires plugins to be useful.
I tend to be more on your side though. I prefer Obsidian to be as streamlined as possible and hate bloat. Last year I asked the community "what should we remove from the app?" And I mostly got feature requests :(
https://x.com/kepano/status/1890957031017730335
It's a hard thing to balance, but what makes me hopeful that Obsidian won't become bloatware is:
1. We're only seven people, we don't have investors, and we plan to stay a small team so we don't have the same growth pressure that Evernote faced. We simply don't have that much bandwidth.
2. The file-over-app approach makes it easier to build opt-in interoperable tools like you describe. We've explicitly focused on shipping things like Obsidian API, URI, and CLI instead of building everything into the app (most other teams in our space seem busy stuffing a bunch of AI junk in their apps). One example is Obsidian Web Clipper, a separate tool we made that has matured into a great separate product.
3. Plugins (both core and community) mean you can make the app as streamlined as you want.