A browser can decide how its own pages react to wheel events. That helps inside the browser, but it does not make File Explorer, VS Code, or another desktop app use the same motion. SmoothScroll operates at the Windows input layer, so the same engine can cover Chrome and the rest of your wheel-driven workflow.
The useful part is not stacking every possible animation. It is choosing one predictable profile. If Chrome already feels good natively, exclude it. If its wheel distance or deceleration feels inconsistent with the rest of your apps, give Chrome a dedicated SmoothScroll profile.