Cassandra in general can't provide guarantee any ordering of the executed queries, since nodes may fail or rejoin the in arbitrary points in time.
But why can't it provide ordering for queries run at at least the quorum level? Given that none of the updates get lost, why would order still an issue? Can you maybe illustrate a scenario which shows how/where the order would get lost if writes and reads always occurred with quorum consistency?