IMHO the most important endpoint for ETH2 isn’t ETH1 under the beacon-chain,
or greenfield projects under the beacon chain, but rather major projects that have already been in development for years, and already had a testnet targeting some alternative sub-chain substrate (e.g. Polkadot, Near), re-evaluating their alternatives at mainnet launch time, and choosing to use ETH2 as their mainnet substrate chain instead.
That could create a lot of momentum/adoption for ETH2, very quickly. And it wouldn’t take much: all these substrate projects are intentionally architected so that you can just develop for them as if you were developing for an ETH1 side-chain, and defer all the operational questions to network launch time. They’ve intentionally commoditized themselves!
So, as long as ETH2 is the best choice for a substrate when these projects go to mainnet, it’s what they’ll pick. And, for many reasons (that all mostly come down to “lifetime cost of bridging to either ETH1 and/or chain-foo-where-DEX-foo-lives”), ETH2 may be the best choice.
(Imagine if you developed your project against some Postgres-ish-DB-aaS cloud provider like Greenplum Cloud, but only used regular Postgres features; and then, when you went to production, you looked around and decided that Amazon RDS was good enough—and on top of that, required no re-engineering, since you weren’t doing anything fancy.)