Okay so the diagram helped!
I now understand that mikrotik is responsible for handling an amount of the traffic from your networks to the ISP modem and to the internet.
However for some network traffic you want to be able to shift that traffic from the MIcrotik to the pFSENSE router and use a DNS the PSFSENSE router is dictating and then out the door, and on a separate public IP.
Here is my take on your situation. Overly complicated!
Why not use the mikrotik to do both?? Get rid of pfsense, the p is for PUNT!!!
ISP1 - Mikrotik interface ether1
ISP2 - Mikcrotik interface ether10
Create
BridgeMikcrotik ether2-5
BridgePFsense ether3-9
Assign
Ip address Bridgemikrotik 192.168.88.1/24 network 192.168.88.0
IP address BridgePFsense 10.60.77.1/24 network 10.60.77.0
IP interface list
WAN
isp1
isp2
LAN
BridgeMikrotik
BridgePFsense
Assign DHCP servers and pools as appropriate.
Routes and Mangles ( a new combo chips & fruit snack I will invent)
There is two ways I would think about doing this and remember I am a complete newb at this router.
- a. assign route rules such that mikrotik is default go to router for internet traffic, with old pfsense route as secondary and not used unless primary fails.
b. mark thru mangle rule oldpfsense traffic and tell it to go through ISP2 with another route rule
OR
2. assign both interfaces mangle rules and route rules separately.
- route mikrotik
0.0.0.0/0
interface: actual gateway IP of ISP1
distance = 1
ping gateway
route oldpfsense
0.0.0.0/0
interface: actual gateway IP of ISP2
distance=2
Mangle Rule for oldpfsense traffic,
Chain - prerouting
Source address 10.60.77.0 ****
In-Interface: LAN
Action TAB
action - mark routing
new routing mark - OldPF
route
0.0.0.0/0
gateway IP - actual IP of ISP2 Gateway
Routing mark - OldPF
OR Approach
- Two routes and two mangle rules…
route mikrotik
0.0.0.0/0
interface: actual gateway IP of ISP1
routing mark - mikrotik_traffic
route oldpfsense
0.0.0.0/0
interface: actual gateway IP of ISP2
routing mark - pfsense_traffic
Mangle Rule for mikrotic traffic,
Chain - prerouting
Source address 192.168.88.0 ****
In-Interface: LAN
Action TAB
action - mark routing
new routing mark - mikrotik_traffic
Mangle Rule for oldpfsense traffic,
Chain - prerouting
Source address 10.60.77.0 ****
In-Interface: LAN
Action TAB
action - mark routing
new routing mark - pfsense_traffic
There you have it, and hopefully the sobs and solars of the world will point out where I have gone horribly wrong. 
**** I am not sure how to actually describe source address as from any IP within the particular LAN is it 192.168.88.0 or 192.168.88.0/0
PS… DNS hmmmmm I am piss poor at understand how DNS works on any router but suggest at the DCHP server settings under the NETWORK TAB, there is a spot, normally blank for you to put in the DNS server of your choice vice the default ISP ones normally used. If I am not mistaken the Mikrotik will use the ones you setup first (can be more than one) prior to using the ISP DNS servers.
On the other hand there is a more direct IP DNS settings tab. Here one can see a blank spot at the top perhaps to add servers and below this it shows the default ISP DNS servers being used.
However at this spot I am not sure what use it is if you have TWO WANS? The DHCP server Network Tab seems more useful in that you are telling each network to use a specific DNS server.
I would like to kinow the purpose and hierarchy of this IP DNS Tab.
For example if one puts a specific DNS server under the IP DNS Tab does that automatically overide the default DNS servers from ISP for all networks?
For example if one puts a specific DNS Server under the IP DNS Tab does that automatcially overide the DHCP SERVER additions one could make at the Networks Tab?
What is the relationship??