The volume of traffic doesn't really matter that much. Developer productivity is just as important as the service you're actually selling when you're the size of Netflix. If your N thousand engineers are suddenly unable to work, or slowed down by X%, that's a huge problem. Large companies treat (or should treat) developer tooling issues as seriously as application outages.
If Netflix is using IPFS for anything worth mentioning, it's almost certainly substantive enough to be considered an endorsement.
Of course the service itself is more important. If there are outages in the service, you will lose customers. If developers lose time at most your new features risk delays. If developers are less productive over time you lose a bit of money.
I say this as a developer for a FANG company.
It’s still an endorsement, but not nearly as strong as if the broadcasting was somehow relying on IPFS. As it is, this is probably just some engineering manager that made some non-crucial tool and put that on ipfs.
If Netflix is using IPFS for anything worth mentioning, it's almost certainly substantive enough to be considered an endorsement.