You have made several interesting points.
Let’s start by agreeing on this: Polkadot is not Ethereum.
That being said, I would take it a step further and say smth very bold, perhaps Polkadot momentarily should be the developer platform for Ethereum and beyond.
I think OpenEVM is half way there. The need is clear. We see the liquidity (Ethereum) and we see the potential (Polkadot).
And so we build an on-ramp for Solidity developers.
In my humble opinion, I have been convinced that the on-ramp is not EVM and that it can be done with ink!. After talking to several Solidity developers they do not see going from Solidity to a Rust-like eDSL language as a hurdle if the use case to deploy to Polkadot is appealing enough.
And so we roll out the red carpet so they can build on us.
We then show them a whole new world: ink!, coretime, cross-chain interopability, ability to scale to a full-fledged dAppChain, we really pop their bubble.
BTW, have you heard of Pop Network? It’s a DOT powered smart contract chain, with primitives to elevate the power of Polkadot to smart contract builders. Developers can compile Solidity contracts using Solang and Pallet Contracts, with further Eth compatibility rolling out as the tech becomes available, but its main core offering is building contracts in ink! using the Pop API. Imagine writing contracts on Polkadot that elevate the power of Polkadot from a parachain level to the smart contract level without all the complexity: Pop API.
We are currently a DF Program candidate. If you think Pop would be useful in our ecosystem then please support us by liking or commenting here:
As an ex-Parity engineer, I have seen us turn away so many gifted developers, teams, and companies that wanted to build on us but we had no answer for: “How do I deploy on Polkadot?”.
With Pop Network, a dot-native chain, one can do this without sacrificing the power of Polkadot.
It is time to blurrrr the lines 
.