These opcodes were being created as combines, meaning they can be created very early. This moves that so that they are created during lowering or the And/Or, meaning other target independent optimizations are more likely to fire, leading to better code.
Making Or and And custom does require some cost adjustments to keep the cost at 1. In the long run, I think it would be good to remove VMOVImm/VBICImm/VORRImm and recognize them during selection.