For me if there really is a need for a hard fork why not go for the 2mb blocksize of Bitcoin Classic?
because a one time bump is just kicking the can down the road and then still needing to ask devs to offer more later.
oliver twist "please sir can i have some more".. then 2 years of waiting for the spoon to feed them
what would be better is even if its not an automated engine in the background
if
core, xt and classic bu, knots and other dozen implementations all had a user options page where users can set their own setting . and that setting appears either as part of their useragent or as a tx versionbit.
then nodes become independent of devs spoon feeding. and consensus can form independently
the dynamic idea is more so an automatic feature so that the even less technical user doesnt need to play around because the nodes
do it themselves. so its not to 'geeky' to use
as for the different versions of nodes.
there is no need for a built-in miner and all the extra pool/mining settings.. if you are just a 'operator'(user).. because there is extra things needed for pools. probably best to think about.. if your not a pool then concentrate just on learning about the version for 'operators'
but its good you are atleast trying to learn about classic core and bu, etc. rather then just getting involved in the social drama
keep it up, there is hope for you yet