We had the same scenario:
- Hosted Feature Layer (with webhook)
- Hosted Feature Layer View (where edit is made).
I can confirm that the edit on the View would trigger the webhook on the underlying service. There was no webhook on the view itself. It might be that you need change tracking enabled on the View item editing settings?

However I would not recommend doing this. As every edit made seems to trigger the webhook, which caused issues doing administrative editing tasks (or if the webhook triggers an edit on the same service, it creates a loop). I've had to adjust the above scenario to the view having the webhook, not the source feature service.
I would instead recommend:
- Never sharing the original feature service nor setting up webhooks on it. This is optimal for data security.
- Create a view, and webhooks on the view itself to trigger when an edit is made against the view.
This way you can better control access to the data and where the edits (e.g. field staff) should trigger the webhook.
If you must have absolutely any edit trigger the event, enable change tracking on your view layers and configure the web hook on the underlying feature service, but I'd still recommend not sharing the original feature service.