You’re welcome. However I wouldn’t be so quick to judge Epic for this.
I think the design rationale was to not clog up AActor with too many unnecessary virtual functions. Firstly, that would explode the code memory space. Secondly, remember that almost everything inherits from AActor. Adding in even one more Tick()-like function would require that almost every object used in the game or editor will have another function that is called every frame interval, which can add up significantly since function calls are expensive compared to inline code (push, pop w/in ASM, but that’s another topic entirely).
Abstract/theoretical coding notions and practices are generally helpful, but they have their exception cases too.