while that makes sense for a static profile, it's 2 complex for MCEBuddy engine to evaluate and adjust on the fly. MCEBuddy looks at the video resolution, cropping and user adjustments to quality to adjust the CQ (qscale or crf) or Bitrate parameters.
In this case, with maxrate, while it works for a known selection, it will be difficult for MCEBuddy to adjust maxrate and CQ on the fly. E.g. CQ the encoder will take care of bitrate based on video type. Putting a maxrate can only be specified for a reference
video, say 720p. Then the resolution changes one can try to change the maxrate, but combined with CQ it may create a mess programtically as there is no way to verify if the paramters are in sync.
Definitely something users can do if they know what kind of profil they are creating and for what video types, but I'm having a hard time visualizing how to combine the 2 for "any" video type thrown at it.