He means run eth1 state and tx verification, but with the the consensus driven by the beacon chain.
The software architecture of this might very well look like an eth2 client and portions of an eth1 client (often called an eth1-engine) running adjunct on the same system, where the eth2-client drives consensus and the eth1-engine handles user layer validity (state, txs, etc).
See this post for a high level on the division of concerns – Eth1+eth2 client relationship