SMART “power on hours” attribute for different HDD manufacturers

I'm not sure what you mean.

• You can ask the disk to run a (SMART) self-test. This usually takes some time, and is somewhat stressful for the disk. I'd not recommend to run it more than once in a long while.

• On the other hand, you can check the SMART status from the disk. In other words, this means "read the SMART meters from the disk". This operation is simple and fast, and can be run how many times you want.

Supposing you are asking for checking the SMART status, then every 60, 30, 15, 10 or 5 minutes, or whatever is good enough. It doesn't matter. In this case, it is more important WHAT will be done with such reading. Will it be logged? Will it be checked for failure and e-mailed when a failure is detected? After all, it makes little sense to read the status every minute if you, the admin, will only look at this once in a month.

If you need help, maybe the smartmontools project might be useful. (at least you can check its source code to see how often smartd reads the status)

In my experience (20 years in operating servers, must have handled about 5.000 disks in all the servers I have dealt with) SMART is useful but no panacea.

If you get SMART errors replace the disk asap. Chances hare very high that with 4-8 weeks the disk will have serious issues. (The Google study frequently mentioned in this regard correlates very nicely with my personal experience.)
Typically you have a week or 2 before the disk becomes really problematic.

If you don't get SMART errors at all, the disk can still fail without any warning whatsoever, although that is quite rare in servers. I see may be 3 or 4 such cases per year. While we replace drives because of SMART errors at about 25/month.
This may have to do that server disks are usually part of a raid array and see a continuous read/write pattern all over the disk. This gets every part of the disk "exercised" (and checked) on a regular basis.
Biggest chance of a disk failing (without previous warning) is on startup if a server has been switched of for some time after been continuously run for months/years.

In consumer equipment (non-server, laptop/desktop-drives) I have seen plenty disks with read-errors that somehow didn't end up in SMART data, even though Windows logged those errors in the Event log. (SMART only did log them after a full chkdsk from Windows.)
This leads me to believe that, in many consumer drives, the SMART thresholds are quite low. This might be (big IF) intentional to keep RMA numbers low in this cut-throat business.
Many consumers will not notice the occasional bad block anyway until it is too late. (How many consumers know where to find the Event log ? That's the only place where you can see disk-errors in Windows.)
In my experience if a consumer disk has issues (SMART or otherwise), copy your data of it and replace it immediately. By the time it gives those errors it is already past dead.