That seems a bit of non-argument. You can choose to keep or remove any components from your codebase, styled or unstyled, composable or monolithic.

What Shadcn gives you is a layer of abstraction that separates the underlying (imported) components from the code that consumes them, so you change your button in one place. It’s exactly how better frontend teams consume just about any component library, Base UI or otherwise.

Shadcn really is a bit of a nothing burger, or rather it’s a bit of soggy lettuce between the meat and the bun.