I believe it is technically a performance optimization to use sealed class over sealed interface (IIRC because of virtual dispatch). I vaguely remember seeing guidance that very large projects with heavy sealed hierarchy usage can benefit from using sealed class, so it would be nice if there was a way to opt out of that check from AbstractClassCanBeInterface.