Including composer custom fields on save draft

I came across another issue: what about the saveDraft() method? somehow there needs to be an observer for the fields added with serializeToDraft() similar to this one:

otherwise the draft will not be sent to the endpoint if only the custom draft fields change.
so saveDraft() should also be part of the api or actually this should be abstracted away somehow.
I also found this dataChanged observer in the composermodel. I think its very odd, that we have two observers watching the same thing. The logic inside this observer would likely also need to be triggered for the custom draft fields. I also wonder which of the two observers will run first and what the implications are.