Maybe you are over-engineering for an MVP?
However there's more than that at play. Let's just assume bootstrapping the basics, with a requirement there's a backend and it has to be deployed:
1. If there's a requirement to have a backend connection and deploy the mvp, that rules out create-react-app / @vue/cli in most cases since it'd be too custom. The app would need to be ejected. But even further, the ejected app is overengineered.
The byproduct of create-react-app's ejected output is so bad I wrote https://github.com/tony/react-typescript-vanilla-starter, https://github.com/tony/vue-typescript-vanilla-starter simply for the sake of getting a minimalist webpack+typescript+hotreload+prod build config working.
I found it challenging to patch together webpack + ts + react/vue from scratch.
2. Going to a stack outside of our usual stack takes time to relearn. Not necessarily a bad thing, but people are going to be rusty.
Te output having to land somewhere. (More than half?) the time pushing dist/ files to a static host won't cut it, even for an MVP. From the beginning, the quickstart tools and workflow become a burden. Cases vary widely, here's mine:
With create-react-app, I don't want to use the included index.html / default dev-server config. I'd be using django-webpack-loader to load the webpack entrypoints. That requires webpack-bundle-tracker [1]
In my case, it'd also involve compiling via webpack, collecting static files and pushing them to S3.
[1] To be fair, you could use https://github.com/timarney/react-app-rewired to add it.