Had similar thoughts and wondered if there were empty/dummy methods declared in the base class to early(ly??) define method signatures similar to interfaces.
As nothing forces you to implement such methods when NOT done via interfaces, it might be necessary, if such methods have side effects expected to work in the fwk. Side effects as pillar of a fwk OTOH are not the typical pattern, to put it mildly, so I do wonder still myself...

>If I understand correctly you are just trying to determine whether the method is overridden in the child class. If so I don't know why you are walking the class hierarchy. If the method exists then you could just use :

return (loMethodInfo.ReflectedType = loMethodInfo.DeclaringType)