FWIW, the app was testing available charge limit methods, to only offer those that can work. Sadly the methods that are not supported are actually preventing charging, but the app is not able to re-enable it. It's actually a bug in the kernel. eg app reads the content of a file, puts 0 in that file, check it's set to 0, puts back 1 in that file, checks it's set to 1, and puts back the original value (read before) and checks it's the same as the one it reads. Files could actually contain other values (enable/disable), but one of those files can disable charging, but it does not allow enabling it back, hence the kernel bug.
I plan to add new filtering capabilities to the app and will add labels at the same time, because labels will need a way to filter, and other criteria have been asked in the past. Filtering by all sorting methods would actually be perfect. And this filtering requires a dedicated dialog box, that would include the old user/system quick filter, labels, and other elements from the sort.