Nope.

Think about the complexity that this would entail in a multi user environment, where the "same" row in a base table could be updated, deleted-then-reinserted, updated later, etc etc. Plus the serialisation that you'd probably need to manage it all.

It's just not practical given the one the premises of materialized view logs in the first place is keep impact on the base table low and defer the effort of populating a summary table (the mview) in an asynchronous fashion.