WinSQLServices looks for any services that have the word "SQL" in the display name. You could modify the Autodiscover filter it uses to include other mssql services if it's missing from detection. You can also just add any Windows service via "Add Other Monitoring" for that server.
Regarding permissions, Windows service monitoring queries Windows itself and does not require it to have access to the underlining application running that service (like you don't need any access to SQL Server to monitor SQL services). You don't need to match the account or permissions the services are running on either.
If your using administrator access for monitoring, you should be able to see and monitoring all services regardless how they are running. In general, if you can see any services at all, you are likely able to see all of them.
That will be different if you are following the newer Principle of Least Privilege and running monitoring with non-admin level permissions. You may need to make permission changes in Windows (again not in SQL) to continue to access Services: https://www.logicmonitor.com/support/getting-started/advanced-logicmonitor-setup/windows-server-monitoring-and-principle-of-least-privilege#h-granting-windows-service-permissions-nbsp-sddl-nbsp-changes