I think, journal classes such as this one are written to simply match the journal print style. I assume they don't have an interface for settings other than needed for the journal, no re-program interface, even clean coding is not needed. They just work for the journal. They are not really tested against other packages. They are for their authors, rather then published for the world.
My way would be choosing an extensive, flexible, multi-purpose class, then modifying the appearance as needed, rather than taking a random journal class just because of it's visual appearance. A Koma Class has features, where a Journal Class has restrictions. Restrictions and limits make the publishers workflow possible, not having to deal with fancy things.
Just thoughts typed on my mobile phone, returning home to my computer, where I can check things above.