I never use hvm qubes because I need copy and paste between qubes and all the other things that makes Qubes OS actually usable as a daily driver.
But I don’t like compromising on security either. How come KickSecure is offered as a community template but not SecureBlue? Does that not call into question Qubes OS’s security position itself?
All it means is that someone made a KickSecure template, and no one made a SecureBlue template. If you think a SecureBlue template is needed, then make it yourself, you are provided the tools to do so.
I think this statement is far stretched. 
SecureBlue is not compatible with Qubes because Qubes is not compatible with Wayland. Qubes uses X11, which is an insecure windowing system (gui stuff). It isn’t insecure on Qubes because Qubes by default negates the vulnerabilities X11 introduces. Qubes doesn’t have a SecureBlue template because until Qubes supports Wayland (work is currently being done, but it is a lot of work) SecureBlue won’t run, even if someone made and packaged a template.
Qubes protects most people against what would normally be covered by a secure guest OS (Template qube). You should separate programs and data into different qubes by trust (and other considerations). I sympathize with wanting more secure templates, but what does a secure template provide that Qubes doesn’t by properly isolating data and programs?
And a simple search in the Forum would have shown exactly this
information.
I never presume to speak for the Qubes team.
When I comment in the Forum I speak for myself.
One can install Secureblue as a Standalone Qube.
I downloaded no Nividia version.
20 GB hard drive. 12 GB RAM in Settings.
I guess there is a question of how the graphics is secure??
Trivalent works.
In trying to run Flatpak, the applications fail with idconfig failed.
I am not going to use Secure Blue, so I am not worrried about solving that.
Cheers.