You can exclude them from installing through an autounattend.xml (see Schneegans.de for help building one) and prevent them from display via a GPO. You really want to use a group policy object because otherwise a Windows Update might put them back; it'll override a plain old registry change or user preference any time it wants but GPO changes persist.
It is trivial to restore Local Group Policy editing on Windows Home SKUs with a little powershell.
Get-ChildItem @(
"C:\Windows\servicing\Packages\Microsoft-Windows-GroupPolicy-ClientTools-Package*.mum",
"C:\Windows\servicing\Packages\Microsoft-Windows-GroupPolicy-ClientExtensions-Package*.mum"
) | ForEach-Object { dism.exe /online /norestart /add-package:"$_" }
Some GPO settings are ignored outside the context of Windows Education or Enterprise SKUs, but most of those are related to user behavior data mining. I can verify that if you're just trying to supress OneDrive, Bing Search and Microsoft Account sign-ins, those are all maintained just fine even on Windows Home.