No it won’t. AFAIK @jdd created an openFate for findgrub a while ago. I can only agree with him. 
Well, I filled some gaps already with updateGrub2 - included in package updategrub. Actually when you install updategrub under 12.1 or lesser, updategrub becomes a symlink to updateLegacyGrub. In 12.2 it will be a symlink to updateGrub2. On 12.1, updateGrub2 can be used to install Grub2 in parallel to Legacy Grub, like in the example I posted in this thread. You’ll just install it in another VBR (excepted the extended one - as far as I recall it doesn’t work). On 12.2 (tested with Milestone3) it can improve Grub2 installation by installing/compiling a missing font and setting up graphical boot menu, and further be used to refresh the boot menu. Of course it can be used for its original purpose of installing grub2-efi.
It’s not impossible that the combination of Perl Bootloader and os-prober will offer both, chainloader (YaST already does) and kernel boot entries. os-prober, as in version 1.52 (12.2 has version 1.49) creates chainloader for Windows and Kernel entries for Linux. I still let generate chainloaders with updateGrub2 but it might - and it should - change. I’ve been considering @nrickert suggestion here:
And it would be actually quite easy to implement. It’s just not a grub2-mkconfig issue, or not only. It requires to add a script in /usr/lib/os-probes, and it’s actually rather simple for a Bash programmer. Take a look at these scripts, James. I’m sure you can add some. I did add 3 already to detect FreeBSD, NetBSD and openBSD kernels. They are useless (but totally harmless) without the appropriate code in /etc/grub.d/30_os-prober. That’s why I added option -b to updateGrub2. This option (which only needs to be run once) will allow grub2-mkconfig (or whatever you call it) to create boot entries for FreeBSD, NetBSD and openBSD. I also had to add ufs2 support in os-prober. This is discussed in this bug report
https://bugzilla.novell.com/show_bug.cgi?id=759635
However there is another (unrelated) bug I mentioned in the bug report but haven’t be able to fix yet. I thought I did but I was wrong. I’ll explain it some day with more details and examples. It doens’t affect ufs2 support, which is working well for me now.
I occasionally have problems mounting Linux partitions (on different machines and under different distros). I haven’t been able to figure out the reason, but mounting again if it fails seems to solve the issue in most cases. Once a partition has be mounted (either manually or by os-prober), the problem disappears.
Because of this bug I encountered with all os-prober versions under all Linux distros, some kernel boot entries might not get added, because the partition where these kernels are located won’t get mounted by os-prober. The only workaround (which always work) is to mount the partition manually once. Than, os-prober will detect the kernel or even be able to mount the partition if you unmounted it in the meantime. I don’t know why. 
I’ve been using os-prober a while ago since updategrub depends on it, before it was available in any other repo, whether release, factory or home repos. For a long time, I just kept building the Fedora version for openSUSE without adding a line of code. But lately I became tired of a couple bugs which bothered me for months … well, that would be years by now, I guess. Thus I started looking at the code and submitting bug reports and patches. However I’m not very good at that. It would be nice if these patches would be passed upstream, because I don’t necessary want to have to install my own os-prober version. Anyway, I made it easy. updategrub still requires os-prober 1.49. So it will run with the version which came with openSUSE 12.2, but with less functionality and more bugs.
Here’s another bug which IMO didn’t catch the attention it deserves: Access Denied. I solved it as well in my os-prober build.
Btw, James, would you mind fixing the typo in the subject?
I hope this post is readable … it looks complicated somehow.