Every opportunity on Vome carries a colour. It is what lets you tell one opportunity from another at a glance on the schedule, in lists, and in chat. Vome picks a colour for you the first time you publish an opportunity, and you can change it whenever you like.

Vome assigns one automatically the first time you publish the opportunity. It works through a fixed set of 15 colours and moves to the next one each time, so opportunities you create around the same time do not all end up looking alike.
That first colour is a starting point, not a fixed property of the opportunity. Once you choose a colour yourself, Vome keeps it and will not reassign it later.
The change applies immediately, everywhere that opportunity appears.
Users see the same colour you pick. This is not an administrator-only setting, so it is worth choosing something readable rather than something that simply looks different from its neighbour.
Yes. In the create and edit workflow, step 2 (Customize) finishes with a Display settings section carrying the same Calendar colour control. You can set it there instead of coming back to the dashboard afterwards.
Yes. On the Opportunities page, select the opportunities you want and open Update schedule settings. The Display settings card there has the same Calendar colour picker, and it applies your choice to every opportunity you selected.
As with every setting in that panel, only the settings you deliberately switch on are written. The rest are left exactly as they were on each opportunity.
A duplicate does not inherit the colour of the opportunity it came from.

Almost always because the shift carries a shift tag that has its own colours.

Shift tags are the right tool when you want to mark a type of work across several opportunities, for example Setup or Cleanup. The opportunity colour is the right tool when you want one opportunity to read consistently everywhere.
Any administrator whose role is allowed to manage schedule settings. If the Edit button on the Calendar colour row does nothing for you, that permission is what is missing, and an administrator who manages roles can grant it.