cancel button on forms is very confusing and frustrating to clients, can we change functionality to cancel only aborts when creating new records?

I have been trying to teach people the usage of the new system, and every person has had the same problem and "hates" the system (till I show otherwise, and the response is the same, "thats stupid"). When creating a new record (like customers, sales orders, invoices), when users want to start over or not save the record, the first thing they do is go for the cancel button... then of course they start panicking because all these red boxes are coming up.

Can we change the action of all cancel buttons where:
- if it is a new, unsaved record, the cancel button only aborts the new record and returns to the list view.
- if the record is a saved draft, prompt the user do they want to cancel or delete, then returns to the list view.

also, when switching back to list view from form view, the system already asks if they want to save, thats perfect, but if the selct no, when it gets back to the list view it is still partially there and continues to ask them if they want to save it or not. if they select no, can it completely abort and refresh the list view? (or have this feature as module also)

once past this hurdle, everyone finds the system easy enough to use.

This would affect both gtk and web clients. If this is not possible, is it possible to create an additional module to override this functionality? I have already created a web hosting module (plan to release to community). This is about the only thing preventing deployment at the moment.