As far as I know, the minimum SDK requirement is Google latest attempt to force app developers to upgrade their apps for enterprise-grade use cases running more recent Android firmware versions , and there is intentionally no  official MDM API defined for any compliant MDM solution to bypass it..

What I expierienced with different customer is the fact that you do't have this Block when there is no network connection outside to google. 
Only if you have an open connection this message appears. 
So maybe if you don't need this connectation. 
That could be a point. 

Hi Bob,

Please be careful if you use 

     adb install --bypass-low-target-sdk-block

to bypass for PRODUCTION devices meant to be managed and protected by MDM/UEM solution .   This approach using ADB is meant for developers with sufficient expertise to do software debugging/development on test devices. If a production device configured with ADB is not subsequently deployed with proper MDM protection policies, it is possible that the security of the device will be seriously compromised when it is used by normal end-users in the field.

Hello Bob S,

Thank you for your post on SOTI Pulse.Thanks Raymond Chan & Leon Callsen for responding to the post, your expertise and willingness to help are greatly appreciated!

It's not possible to perform this on the MobiControl End and as suggested on the above posts it's not a recommended method to perform on the enrolled devices. For more information as below

I would like you to create a support case (click here) or call the SOTI Support team (click here)  to gain a better understanding of the issue. We can then determine whether to raise a Feature Request or troubleshoot to fix the issue.

Please let us know so we can proceed further accordingly.