pezetkoconceptually it may feel analogous, however ICE is bigger beast than that. In VOP/VEX operator you can either do multithreaded operations over points/prims/vertices/numbers or singlethreaded operation (detail)
… And ICE tree is just single Operator (like AttributeVOP)….
in ICE you can mix and match them as many as you want so in single operator you can do some parallel operations on your point attribute array, then get min/max, normalize, use that to build new topology object, then change that topology few times, use it as lookup for other operations (in VOPs it would need to be different VOP networks/wrangles), simply it feels like large part of SOPs/VOP funcionality in the same network type, which can be much more powerful than SOPs/VOPs combo, but at the same time can be more messy and simply different but it can be built to feel like SOPs if needed. The truth is as well, that it's not so easy to make it communicate with other ICE operators, but that is more like a specific ICE issue than an architecture problem