So the transactions were not mined when there was spare capacity, the block was not fully utilized and the transactions linger in memory because other miners deemed them too low fee? Nothing here singles out ocean as a positive: they wasted block capacity, the lingering transaction will likely eventually still confirm, and in the meantime they float in the mempool and waste cycles of other miners trying to build a block template.

Ocean behaves just like any normal miner, foregoing transactions it doesn't seem valuable. It's only their cost function is changed, which in a distributed system may cause unexpected effects (heterogenous policies as an attack vector is quite common).