Yes, that is on the roadmap when we switch from the old Kohana QB to our new QB (which is fully platform independent).
You wouldn't want to remove the limit() functionality, as that will also remove it from SELECT statements and will render the ORM virtually useless.
It has to be removed from the UPDATE and DELETE methods. I can only assume it's in there because in the "old" days you could call the method without an id, causing it to generate a "DELETE ALL". The second reason for it being there is that it's faster on a non-index column, as it stops after the first operation, instead of doing a table scan to see if more values match.