I can't think of any conflicts that may result from this change. I realise that most (all?) of the native DOM events that jQuery explicitely supports (e.g.  click, mouseover, mouseout,  load) are already available in jQuery.attrFn, but adding custom events is still a nuisance... this would make it so much simpler:

jQuery('<div/>', {
    bind: {
        customEvent: function(){}
    }
});
​