The other approach to configuring the initial state could be runtime initial genesis config preset (introduced in #2714).
With this chopstick step would not be necessary , and 2nd step (generate chainspec) could be like this:
chain-spec-builder -c output/chainspec.json create -n poc-runtime -i poc-runtime -r ./output/poc_runtime.compact.compressed.wasm -s named-preset name-of-the-config
where name-of-the-config could be the name of preset used for local development, staging or local testnet, etc…
Would that be useful for developing runtime scenarios with omni-node?