So I have been fiddling/tinkering/messing with the Clamshell some more
and im pleased to report that I was able to overclock the bus from 66Mhz to 100Mhz
I figured out how to do so with the help of this guide:
http://web.archive.org/web/20070825055749/http://homepage.mac.com:80/ytotsuka/FW.html (I came across this guide many moons ago but never saved it. it took much internet sleuthing and a trip to the web archive to find it again LOL)
this guide is for FW Clamshells but luckily for us the exact same resistors exist on First gen non FW iBooks

next time I open up the iBook ill grab a picture of my mod since the picture in the guide is not very clear. (im kinda curious what R60/61 does... its a real shame we dont have schematics for these machines, my Macintosh logic-board schematic collection only goes as far back as the GigE TiBook...)
im not all that surprised that I was able to hit 100Mhz even on my early First Gen iBook G3. the Uninorth 1 chipset is a very stable chipset and is known to clock to 120Mhz and even 133Mhz if your lucky, in sawtooths(sawteeth?). I suspect the reason the person in the original guide could not hit 100Mhz was because he did not change his CPU multipliers and I doubt his 366Mhz 750CXe could run at 550Mhz. (66.6*5.5=366Mhz 100*5.5=550Mhz)
since I have a 533Mhz Rated 7410 from a PMG4 DA, I left my multiplier/PLL resistors alone at 4.5x which at 66.6Mhz=300Mhz, but at 100Mhz=450Mhz giving me a nice little cpu "overclock" as well
one of the quirks of overclocking Uninorth 1 Macs is that OpenFirmware and as such Mac OS 9/OS X does not recognise/display the frequency change, so for example in my iBook, OS9/OS X still reported 66Mhz/300Mhz clock speeds but using a tool like Gauge Pro or Metronome shows the actual Bus speed is indeed running at 100Mhz and the CPU at 450Mhz and in OS X running GeekBench I saw a nice bump in my score to what id expect for a 100/450Mhz G4 system
while this is just a cosmetic thing for the most part it would still be nice if the OS reported the true speed, luckily there is a way to do this using an nvramrc script in OF

note the nvramrc script itself is not entirely my own work but i have edited it quite a bit to make it work for this machine setup. my version is just for uninorth machines with a 100Mhz bus speed and a 4.5x CPU multiplier the original work can be found here

:
http://www.xlr8yourmac.com/G4ZONE/sawtooth/SawtoothCPUdesign.html. if your overclocking the bus on a stock iBook G3, then replace PowerPC,G4 with PowerPC,750
first boot into OpenFirmware
then type nvedit<return> then type the following (<return> means you hit the enter/return key):
- " /" select-dev<return>
- 05f3e27a " clock-frequency" get-my-property 2drop !<return>
- " /cpus/PowerPC,G4@0" select-dev<return>
- 1ad27480 " clock-frequency" get-my-property 2drop !<return>
- 05f3e27a " bus-frequency" get-my-property 2drop !<return>
- 017cf89f " timebase-frequency" get-my-property 2drop !
then once you have got all that done
do the keyboard combo "ctrl c" to exit the nvramrc editor.
then at the OF prompt(this saves the script to NVRAM):
nvstore<return>
then (this tells OF to use the script):
setenv use-nvramrc? true<return>
then finally (this reboots the machine

:
reset-all<return>
if you have done everything correctly then you should see Mac OS 9/OS X reports the right clock frequencies
its worth noting this is low level OpenFirmware stuff if you make a Typo (dont forget the spaces!) you could brick your machine if you cant reset your PRAM/NVRAM, if you dont feel comfy messing around in OF like this, you dont have to use this script its for the most part just cosmetic fixes
and also since this is an NVRAM thing, if you lose/reset your NVRAM you lose this script as well. if you want to keep the script in NVRAM but turn it off for something, you can do
setenv use-nvramrc? false<return>
this tells OF not to use nvramrc, and as such will ignore the script in it.
also if you want to make edits or make sure you have not made a typo somewhere, you can use the arrow keys while in nvedit to navigate and edit each line. (I recommend you do this before saving the script to nvram with nvstore)
now with all the technical mumbo-jumbo out of the way time for some pictures
here is the iBook with the FSB overclocked but without the nvramrc script, you can see Mac OS 9 still thinks the machine is running at 66/300Mhz but as you can see using tools like gauge pro/Metronome we can see the real clock frequency
here is Mac OS 9 with the nvramrc script, now it reports the correct frequency
here is OS X 10.5.8 Leopard with the nvramrc script
and heres a GeekBench result at 100/450Mhz
https://browser.geekbench.com/geekbench2/2652202
im also happy to say that the machine has been 100% stable for me with no issues, the iBooks stock cooling even manages to Just about keep the 7410 now clocked at 450Mhz happy

(thats another thing that tells me it is really running at 100/450Mhz as the system does run warmer)
this is one properly souped up iBook now I think

(and possibly the only Clamshell in the world with a 100Mhz bus speed, for now at least

)