fvwm95 was a fork of fvwm2 and has remained in that state, and never updated.
It was created at a time when the theming in fvwm was not as flexible, but it's completely possible to emulate all of fvwm95 in fvwm3, and behind the scenes, the application support in fvwm3 greatly outweighs the version of fvwm2 which fvwm95 wad forked from.
In other words, it remains a curio in fvwm's history, and that's where it should remain.
True -- but then, FvwmButtons was never meant to compete with systray stuff, the original spec came via EWMH for that. and didn't really affect FvwmButtons' raison d'être.
Yes -- same with CPP as well. Fvwm2 allowed you to use the language features of M4/CPP to hold variables and to perform loops on different data, so you could generate complex config files that way, without needing to build that into the core config syntax itself.
However, in fvwm3, I've removed both those modules.
It was created at a time when the theming in fvwm was not as flexible, but it's completely possible to emulate all of fvwm95 in fvwm3, and behind the scenes, the application support in fvwm3 greatly outweighs the version of fvwm2 which fvwm95 wad forked from.
In other words, it remains a curio in fvwm's history, and that's where it should remain.