1. More of a heads up but storage requirement will never be trivial, even with fs compression. Browsers limit resource cache for a reason.
2. Unless OneNote has some kind of page nesting functionality beyond the usual outline/TOC tagging, typical browser-history population and web page length can lead to an infinitely-scrolling, memory eating, difficult to use note.
3. It is easier to lean on existing browser and filesystem functionality by printing to PDF and optionally attaching wherever (such as onenote) for a number of reasons.
4. Visual consistency of the print render will vary, but the PDF approach uses existing render in situ and is the only page snapshot commonly supported by progressive web applications.

Besides PDF, the most consistent local full-page, full-asset save I’ve found is the .archive format. It’s used in the Safari browser for local saving and is the basis for features like “Add to reading list.” Archive appears to be something like a zipped wget directory but includes additional session state information for future page recreation. I save both PDF and Archive formats and browse using filesystem rather than another app like onenote.

If you’re on Windows, this appears to be the aim of their Recall feature. Just be aware that it (and really that entire operating system) comes with a lot of privacy-related concerns.