The cut operation will still trigger a change event, so you can detect the cut operation via its range event argument -- if all cells in the range are empty, the row has been deleted. There will be the same outcome if the user hits a delete key, so checking the values will handle this case, too.
As for the change event, we are currently evaluating how to allow detection of the row delete / insert. The change event may need to be triggered with all subsequent data, or we might provide additional events for these actions. We do not have a timeframe for the implementation, but it is likely to happen in future internal builds. We will respond in this thread once this is fixed.
Join us on our journey to create the world's most complete HTML 5 UI Framework - download Kendo UI