I think this datapack took at least 1 year to make lol

Would it be possible for a datapack to make every item drop have a nametag? What I mean by this is if you see some dropped pork it would have a name tag letting you know that's what it was. I think this idea would really go along with this datapack you have created here.

I feel like this datapack is aimed at new players and as such, have you ever considered on making a data pack that puts a link to the item or block's wiki page in chat whenever you first obtain the item/block?

not tested, but opened the code, looks cool.

some critique:

dividing into separate functions:

the starting part of each command in "ids_scoreboard_blocks_air_1.mcfunction" is the same. You should try dividing some things into separate functions to decrease file size?
execute as @e[type=player,scores={visor_toggle=1}] at @s anchored eyes positioned ^ ^ ^1 run execute if block ~ ~ ~ minecraft:birch_sapling run scoreboard players set @s visor_facing_id 21to where it only executes the first part then runs a function?:
execute as @e[type=player,scores={visor_toggle=1}] at @s anchored eyes positioned ^ ^ ^1 run function idvisor/blocktestwhere blocktest.mcfucntion is the last part of each command.
execute if block ~ ~ ~ minecraft: run scoreboard players set @s visor_facing_id 1

execute if block ~ ~ ~ minecraft: run scoreboard players set @s visor_facing_id 2

...this way you probably only need 2 functions/commands deciding block locations, and 1 function for detecting what block. but maybe there is some unforseen consequenses that i dont know, that makes your current solution better?

why is scoreboards needed?

if you’re not planning to increase performance by only running the block check once, and then wait for movement or something before checking again, i see no reason to use scoreboards. you should just out right run the tellraw command after checking the block type?