- Screenshot button *probably* depends on issue 118 (Although I'm not sure even that'll be enough: Does libnx support screenshots ? Given that HBL destroys the album, I wouldn't be surprised if it didn't).
Ah, the retroarch "everything that doesnt work, may not be needed" approach.

*jk* (but then with a tiny bit of sarcasm pointing at an inkling of truth..

).
- Having the screen shot button work is not a thing to be overlooked, imho. Its a dedicated button on the device. With a dedicated purpose. That serves a function the system is built to provide - independent of the software/app running. Putting all files in the same dedicated place for viewing, easy sharing - copying to a different location... Its no small feat. Its a major feature of the Switch. Its what Retroarch didn't manage to do in the 13 years after facebook came out - in terms of sharing your experiences, easily, with other people.
The feature has a dedicated face button on the front of the device. So before you pronounce that button "useless", because why not ignore it, if it doesnt work currently, lets take a pause. Look at the situation. Reevaluate.
Now back to answers.
- The button (/framework of stuff it does) does indeed seem to be supported by libnx - at least the button works as expected in pFBA, and that apparently is libnx based.
- HBL does indeed "destroy" the album function, but only if the exploit is loaded. If you reboot, screens you took in pFBA show up in the Switch' album, and can be viewed/manipulated from there.
- HBL also "destroys" the Switch' game launching function, if the exploit is loaded - btw, so expect people to restart their switches quite a bit to switch between "exploit loaded" and "not loaded" for quite a while.
- HBL highjacking the album icon is about the stupidest thing I've ever encountered in "system integration decision making". Idk if there are underlying issues - but the guy who thought it would be a good idea, to "destroy" the gallery function, to be able to launch homebrew, can collect a paragraph of verbal scolding, anytime he wants to.
We have had half inspired, half working, retroarch ports on different systems, that didn't care about a systems capabilities or a solid implementation to fill a freight shipping container with. How about we (I say we - without being able to actually code :/) make the Switch port not one of those?
The Switch is quite a popular system actually - thats portable, and very likely will be fully opened at some stage in its lifetime. That will serve as a callingcard for Retroarch for years to come. Treat the thing with respect. Think about its capabilities (Portable, 1 controller that can become 2 controllers, usable in vertical and horizontal mode, likely capable of up to Dreamcast level emulation, biggest screen for a popular portable gaming platform so far, screen shot feature built in, ...).
Thank you for the consideration.
(Not directed against you, but there is quite a bit of built up anger on how emulation became "more platform independent" because of retroarch in the past - and what this meant for its implementation on different systems built up here.

(Retropie is a mess. No one cared about input lag, usability, interface design -- and yet its probably the most wide spread emulation experience most people have had today...).)