Yes, that is correct.

There exists a workaround: With a database trigger on the table for the entity at the top of the subclass hierarchy, the end revision timestamp can be copied to the corresponding subclass tables. However, the use of database trigger may not be allowed in some environments. And whenever the class hierachy changes, the trigger has to be changed accordingly, which is error prone.